Thank you Sumanth Just raised https://issues.apache.org/jira/browse/NIFI-1296 so you can track it and contribute if you have more details/expertise. My biggest concern is compatibility with older brokers. Currently even though we’ve upgraded to 0.9 it is still compatible with 0.8 brokers for obvious reasons. Do you know if using new consumer API will still work with 0.8 brokers? I’ll investigate anyway, but any input would be appreciated.
Cheers Oleg On Dec 16, 2015, at 6:19 PM, Sumanth Chinthagunta <[email protected]<mailto:[email protected]>> wrote: Hi Oleg, For my case NiFi (consumer) has to talk to Kafka cluster behind firewall and it was difficult got Kafka brokers and ZooKeeper ports opened. I noticed that 0.9.0.0 support consumers directly communicate to Kafka brokers with `bootstrap.servers` setting. it might be good idea if you consider to upgrade GetKafka also to new consumer API to avoid firewall hassle. Thanks Sumanth On Dec 16, 2015, at 9:50 AM, olegz <[email protected]<mailto:[email protected]>> wrote: GitHub user olegz opened a pull request: https://github.com/apache/nifi/pull/143 NIFI-1218 upgraded Kafka to 0.9.0.0 client API Tested and validated that it is still compatible with 0.8.* Kafka brokers You can merge this pull request into a Git repository by running: $ git pull https://github.com/olegz/nifi NIFI-1218 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/143.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #143 ---- commit 10cbc92873784a4a3871ae6937b8a43ac3e0abe8 Author: Oleg Zhurakousky <[email protected]<mailto:[email protected]>> Date: 2015-12-16T17:49:44Z NIFI-1218 upgraded Kafka to 0.9.0.0 client API Tested and validated that it is still compatible with 0.8.* Kafka brokers ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at [email protected]<mailto:[email protected]> or file a JIRA ticket with INFRA. ---
