[ 
https://issues.apache.org/jira/browse/ATLAS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viktor Somogyi-Vass updated ATLAS-3864:
---------------------------------------
    Description: 
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.

  was:
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 though it is possible to continue 


> 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)

Reply via email to