[
https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503179#comment-14503179
]
Jordan Zimmerman commented on KAFKA-873:
----------------------------------------
[~nehanarkhede] - the major upside with Curator (note: I'm the main author) is
in the Framework, not necessarily the recipes. Writing correct Zookeeper
applications is notoriously difficult. Curator manages the internal ZooKeeper
connection for you which is not trivial. Curator also incorporates workarounds
for many well know edge cases. Regardless of whether you use Curator or not
writing your own wrapper over the Zookeeper Java client would be a major
mistake.
> 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)
