[
https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705044#comment-14705044
]
Flavio Junqueira commented on KAFKA-873:
----------------------------------------
Ah! That's what I was looking for, thanks Jordan. What I've noticed is that the
ZkClient bridge alone is not going to do it because it is only a different
implementation of IZkConnection, so the client code is still the same. I'd need
to remove the ZkClient listeners to use the recipe you suggest, but it sounds
ok because I just need to initialize PersistentEphemeralNode once (funny name,
btw). For this jira here, I'm trying to determine if it makes sense to do this
intermediate step through the bridge or go directly into removing the listeners
and add calls to curator framework directly.
> 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)
