atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayendra Parab (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (ATLAS-3864) Atlas should use AdminClient where possible
Date Mon, 02 Nov 2020 15:23:00 GMT

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

Jayendra Parab resolved ATLAS-3864.
-----------------------------------
      Assignee: Jayendra Parab
    Resolution: Fixed

Fixed as part of https://reviews.apache.org/r/72671/

> 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
>            Assignee: Jayendra Parab
>            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)

Mime
View raw message