kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flavio Junqueira (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-873) Consider replacing zkclient with curator (with zkclient-bridge)
Date Mon, 03 Aug 2015 11:39:06 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651764#comment-14651764

Flavio Junqueira commented on KAFKA-873:

Let me elaborate on my suggestion. Adopting Curator doesn't preclude the development of a
Kafka wrapper (e.g., like we have done in apache bookkeeper), and as I understand it, Curator
has done a better job at keeping track of the changes in the zookeeper releases. For example,
I believe zkclient still depends on 3.4.3. I also think that the pluggable mechanism is an
orthogonal effort that could eventually replace all this, but here we already have a patch
at least.


> 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
>             Fix For: 0.8.3
> 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

View raw message