You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Rajini Sivaram (JIRA)" <ji...@apache.org> on 2017/12/06 15:40:00 UTC

[jira] [Commented] (KAFKA-5722) Refactor ConfigCommand to use the AdminClient

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

Rajini Sivaram commented on KAFKA-5722:
---------------------------------------

[~viktorsomogyi] Are you planning to submit a KIP for this? It will be very useful to get this in at the same time as [KIP-226|https://cwiki.apache.org/confluence/display/KAFKA/KIP-226+-+Dynamic+Broker+Configuration], so please let us know if we can help in any way. Thank you!

> Refactor ConfigCommand to use the AdminClient
> ---------------------------------------------
>
>                 Key: KAFKA-5722
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5722
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Viktor Somogyi
>            Assignee: Viktor Somogyi
>              Labels: kip, needs-kip
>             Fix For: 1.1.0
>
>
> The ConfigCommand currently uses a direct connection to zookeeper. The zookeeper dependency should be deprecated and an AdminClient API created to be used instead.
> This change requires a KIP.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)