[ https://issues.apache.org/jira/browse/ATLAS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222237#comment-17222237 ]
ASF subversion and git services commented on ATLAS-3864: -------------------------------------------------------- Commit b1e76ba877b2d2cf0359dfdc2e34b3542b68067f in atlas's branch refs/heads/branch-2.0 from Jayendra Parab [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b1e76ba ] ATLAS-3864 : Break the dependency between Atlas and Kafka's Zookeeper Signed-off-by: nixonrodrigues <ni...@apache.org> (cherry picked from commit d4b15c7a2ab47d64a49070fab766a95497db4f0f) > Atlas should use AdminClient where possible > ------------------------------------------- > > Key: ATLAS-3864 > URL: https://issues.apache.org/jira/browse/ATLAS-3864 > Project: Atlas > Issue Type: Improvement > Reporter: Viktor Somogyi-Vass > Priority: Major > > Zookeeper access should be restricted wherever possible as going forward > Kafka won't use Zookeeper (see > [KIP-500|https://cwiki.apache.org/confluence/display/KAFKA/KIP-500%3A+Replace+ZooKeeper+with+a+Self-Managed+Metadata+Quorum]). > Also the Zookeeper classes in Kafka aren't public apis so usage should be > avoided wherever possible. As a tactical fix (see ATLAS-3910) though it is > possible to continue using KafkaZkClient as that class likely won't change > much until the completion of KIP-500. -- This message was sent by Atlassian Jira (v8.3.4#803005)