[ https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705096#comment-14705096 ]
Flavio Junqueira commented on KAFKA-873: ---------------------------------------- ZkClient is used in a number of places across the code base and using the bridge would let us have a smoother transition over a few jiras. But, using the bridge still requires ZkClient and Curator co-existing, so the approach of replacing ZkClient with Curator gradually without the bridge would also work fine. I was thinking that using the bridge would make the transition easier because the PR already exists for this issue, but I can be convinced that this intermediate step isn't entirely necessary. As I understand it, this issue has been proposed so that we could use Exhibitor with Kafka, which depends on Curator I believe. > 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)