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, 04 Jul 2016 14:35:11 GMT

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

Flavio Junqueira commented on KAFKA-873:

I see what you're saying. That support in in zkClient was added specifically for our needs
in Kafka. It is correct that it is more flexible to do the Curator way, but I'm not sure how
we would be able to benefit from it in Kafka given that this security configuration is internal
to the brokers. If you have any specific idea, let me know and we can see if it is feasible.

> 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

View raw message