[
https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706573#comment-14706573
]
Ismael Juma commented on KAFKA-873:
-----------------------------------
The compatibility story is a bit complicated, particularly if @Beta methods are
used:
https://code.google.com/p/guava-libraries/wiki/Compatibility
It does seem like shading may be an alternative as suggested by [~fpj]. If it's
done at the `Curator` side, then it doesn't affect us much (aside from a bigger
jar for the `Curator` dependency). That would lead to the next question: is
introducing the `Curator` dependency OK or would we want to shade that too?
> 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)
