You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Andras Katona (Jira)" <ji...@apache.org> on 2020/12/07 14:34:00 UTC
[jira] [Commented] (ATLAS-3864) Atlas should use AdminClient where
possible
[ https://issues.apache.org/jira/browse/ATLAS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17245239#comment-17245239 ]
Andras Katona commented on ATLAS-3864:
--------------------------------------
Hi,
I've added a bit of a modification: https://reviews.apache.org/r/73071/
Complete elimination of zk client from atlas. (It's required for Kafka dependency upgrade)
> 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)