You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Stevo Slavic (JIRA)" <ji...@apache.org> on 2016/07/04 11:24:11 UTC

[jira] [Commented] (KAFKA-873) Consider replacing zkclient with curator (with zkclient-bridge)

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

Stevo Slavic commented on KAFKA-873:
------------------------------------

One pro-Curator benefit to note - it seems easier to provision ZooKeeper client authentication to Curator than to ZkClient, out of the box not limited to JAAS config file only.

> 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)