[
https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704220#comment-14704220
]
Grant Henke commented on KAFKA-873:
-----------------------------------
Hi [~fpj], I would be happy to help get this in, any way I can. Especially if
it solves a few other issues at the same time. I agree that getting curator in
can be done now, utilizing the bridge, and then going forward we can define any
pluggable mechanisms or wrappers by utilizing the KIP process if needed.
[~atdixon] submitted the pull request for the patch. If he is still interested
in working on it, it may need a rebase and I will post some comments on the
patch. If he is not, I am happy to rebase and address any comments you may
have. Any help is definitely appreciated. If you would like to take the reigns
on this, feel free as well.
> 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)
