[
https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704731#comment-14704731
]
Flavio Junqueira commented on KAFKA-873:
----------------------------------------
[~granthenke] I'm more than happy to let you take care of this one, but I'd
like to be involved because I want to make sure that we fix KAFKA-1387 properly
and the switch to curator by simply using the bridge might either break kafka
if the semantics of the API are different or not fix KAFKA-1387. What I might
need to do is to wait until this issue here is fixed and then fix KAFKA-1387,
so I'd like to have this one in soon if possible. I'll have a look at the
Curator bridge today in any case.
> 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)
