[
https://issues.apache.org/jira/browse/ATLAS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17250123#comment-17250123
]
ASF subversion and git services commented on ATLAS-3864:
--------------------------------------------------------
Commit ab92cf1e6db021e83d8b42ac559f077ab17afa65 in atlas's branch
refs/heads/master from Andras Katona
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=ab92cf1 ]
ATLAS-3864: Follow up change, removed remaining usage of zkclient even from poms
Also removing kafka core dependency from kafka-bridge since it's not used any
more
Signed-off-by: nixonrodrigues <ni...@apache.org>
> Atlas should use AdminClient where possible
> -------------------------------------------
>
> Key: ATLAS-3864
> URL: https://issues.apache.org/jira/browse/ATLAS-3864
> Project: Atlas
> Issue Type: Improvement
> Affects Versions: 2.1.0
> Reporter: Viktor Somogyi-Vass
> Assignee: Jayendra Parab
> Priority: Major
> Fix For: 3.0.0, 2.2.0
>
>
> 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)
