You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Ramesh Mani (Jira)" <ji...@apache.org> on 2020/09/18 01:57:00 UTC

[jira] [Assigned] (RANGER-3001) Update Ranger KafkaClient to use Kafka AdminClient API instead of Zookeeper

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

Ramesh Mani reassigned RANGER-3001:
-----------------------------------

    Assignee: Ramesh Mani

> Update Ranger KafkaClient to use Kafka AdminClient API instead of Zookeeper
> ---------------------------------------------------------------------------
>
>                 Key: RANGER-3001
>                 URL: https://issues.apache.org/jira/browse/RANGER-3001
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 2.2.0
>            Reporter: Ramesh Mani
>            Assignee: Ramesh Mani
>            Priority: Major
>
> Update Ranger KafkaClient to use Kafka AdminClient API instead of Zookeeper.
> This would have the following benefits:
>  * Security: all Kafka commands are channeled and authorized through the broker instead of direct Zookeeper data manipulation. When topics are generated via Zookeeper, it might happen that even Kafka cannot access to the metadata due to ZK ACLs.
>  * Simplicity/maintainability: the interface of Kafka becomes smaller and there is no need to expose Kafka's own Zookeeper quorum but kept as an implementation detail for storing metadata.
>  * Compatibility: zookeeper in Apache Kafka will be removed in a future version.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)