[
https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361433#comment-15361433
]
Stevo Slavic commented on KAFKA-873:
------------------------------------
Even with latest 0.10.0.0 Kafka clients, explicit topic management requires
using AdminTools and working with ZkUtils/ZkClient.
I guess better course of action (than switching dependency now) is to work on
topic management broker API, to be able to remove ZK dependency from clients
and tools completely, make only brokers talk with ZooKeeper. So work on
https://issues.apache.org/jira/browse/KAFKA-2945 and likes in
https://issues.apache.org/jira/browse/KAFKA-1694
After that, it will be also easier to abstract away in Broker metadata storage
and coordination.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-30+-+Allow+for+brokers+to+have+plug-able+consensus+and+meta+data+storage+sub+systems
> Consider replacing zkclient with curator (with zkclient-bridge)
> ---------------------------------------------------------------
>
> Key: KAFKA-873
> URL: https://issues.apache.org/jira/browse/KAFKA-873
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.8.0
> Reporter: Scott Clasen
> Assignee: Grant Henke
>
> If zkclient was replaced with curator and curator-x-zkclient-bridge it would
> be initially a drop-in replacement
> https://github.com/Netflix/curator/wiki/ZKClient-Bridge
> With the addition of a few more props to ZkConfig, and a bit of code this
> would open up the possibility of using ACLs in zookeeper (which arent
> supported directly by zkclient), as well as integrating with netflix
> exhibitor for those of us using that.
> Looks like KafkaZookeeperClient needs some love anyhow...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
