[
https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535675#comment-14535675
]
Tom Dyas commented on KAFKA-873:
--------------------------------
If there is some doubt as to whether Kafka should be switched to Curator, a
better choice may be to implement a mechanism by which the library user can
supply the ZkClient to use instead of making it a singleton. Then a user that
wants to use Curator can simply provide a constructed ZkClient (bridging to
Curator) to Kafka.
I would love to be able to use Curator simply to allow Kafka to share the
Curator ZK connection already used by our application code. This will help
reduce the number of connections to our production ZooKeeper cluster.
> 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)
