Support Questions
Find answers, ask questions, and share your expertise

Apache Nifi on QNX

New Contributor

I have been reading how Apache NIFI will solve the problems on getting sensor data from the cars and filtering them. Also how NIFI configured to manage the bidirectional data flow (requesting more information from a specific car unit, for example, http://www.zdnet.com/article/hortonworks-cto-on-apache-nifi-what-is-it-and-why-does-it-matter-to-iot... .

How come the car sensor data is the example to demosntrate NIFI's capabilities when NIFI requires JVM and QNX (the main OS in cars)actually does not support JAVA?

1 ACCEPTED SOLUTION

@P C

I share your view that there are a number of scenarios for which a JVM based dataflow management tool would be unfit or suboptimal.

Recognizing that and a number of other unique challenges that exist in the edge collection space, the Hortonworks DataFlow team is working as part of the Apache MiNiFi community that Matt just mentioned. MiNiFi is a subproject of Apache NiFi and is designed to work seamlessly with NiFi.

To your specific question asking if Hortonworks is developing any support for QNX I can state that we are supporting a range of IoT and 'metal that moves' cases as mentioned in that article. A recent public example of our efforts in this area can be found in this article https://hortonworks.com/blog/qualcomm-hortonworks-showcase-connected-car-platform-tu-automotive-detr...

Thanks

View solution in original post

5 REPLIES 5

Super Guru

Here's my answer from StackOverflow:

There is a subproject of Apache NiFi called MiNiFi, which (among other things) aims to have agents on devices and such in order to collect data at its point of creation. This will include native agents, thus a JVM will not be required. The proposed roadmap is here, it mentions the development of native agent(s).

New Contributor

This doesn't actually solve my question. Is Hortonworkds actually developing any support for QNX? Otherwise, the statements in this article wouldn't make much sense :). http://www.zdnet.com/article/hortonworks-cto-on-apache-nifi-what-is-it-and-why-does-it-matter-to-iot... . The mayority of the IoT clients do not suppport JVM.

@P C

I share your view that there are a number of scenarios for which a JVM based dataflow management tool would be unfit or suboptimal.

Recognizing that and a number of other unique challenges that exist in the edge collection space, the Hortonworks DataFlow team is working as part of the Apache MiNiFi community that Matt just mentioned. MiNiFi is a subproject of Apache NiFi and is designed to work seamlessly with NiFi.

To your specific question asking if Hortonworks is developing any support for QNX I can state that we are supporting a range of IoT and 'metal that moves' cases as mentioned in that article. A recent public example of our efforts in this area can be found in this article https://hortonworks.com/blog/qualcomm-hortonworks-showcase-connected-car-platform-tu-automotive-detr...

Thanks

New Contributor

Wow, how can somebody else accept an answer on my question? That doesn't make sense. It is still not clear to me the approach to take and I would need further research in order to clarify all the nuances...

New Contributor

Hortonworks has MiNiFi C++ https://github.com/apache/nifi-minifi-cpp

it is native implementation of MiNiFi, we compile under linux, OS X, Raspberry PI.

Please see the README.md for system requirement for the same.

As for as QNX support, if QNX development environment have a cross compiler/packages which meet the above system requirements, porting the MiNiFi should be feasible and not a big task to accomplish.

; ;