[jira] [Commented] (ATLAS-457) Upgrade to 0.9 version of Kafka dependency

["Hemanth Yamijala (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ATLAS-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119131#comment-15119131 ] 

Hemanth Yamijala commented on ATLAS-457:
----------------------------------------

Attached the patch on review board here: https://reviews.apache.org/r/42851/

The changes are:

* Renamed a constant that is unavailable in the latest version.
* The KafkaServer launch API required a change in the way it was initialized
* The Kerberos security tests {{NegativeSSLAndKerberosTest}} and {{SSLAndKerberosTest}} of Atlas started failing. This was because when we bind the Config option {{java.security.auth.login.config}} to the JVM running the test, Zookeeper and Kafka also attempt to run in secure mode. The tests only attempt to configure Kerberos for Atlas. Hence to simplify, I disabled Zookeeper security as was suggested was someone in ZOOKEEPER-1764 - which works for us as well. We would of course need a different JIRA to ensure we run with secure Kafka correctly. But I think that could be a separate JIRA. Hope this is OK. 

> Upgrade to 0.9 version of Kafka dependency
> ------------------------------------------
>
>                 Key: ATLAS-457
>                 URL: https://issues.apache.org/jira/browse/ATLAS-457
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Hemanth Yamijala
>            Assignee: Hemanth Yamijala
>
> Atlas is using a very old version of Kafka client (0.8.2.0). To keep up with improvements made in Kafka, it would be nice to move to the latest version. Another motivation is that the Atlas Storm integration faces issues when later versions of Kafka is used to build the topologies whose metadata needs to be captured.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)