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

Posted to jira@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2018/02/03 00:33:00 UTC

[jira] [Resolved] (KAFKA-6494) Extend ConfigCommand to update broker config using new AdminClient

     [ https://issues.apache.org/jira/browse/KAFKA-6494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson resolved KAFKA-6494.
------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.2.0)
                   1.1.0

> Extend ConfigCommand to update broker config using new AdminClient
> ------------------------------------------------------------------
>
>                 Key: KAFKA-6494
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6494
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Rajini Sivaram
>            Assignee: Rajini Sivaram
>            Priority: Major
>             Fix For: 1.1.0
>
>
> Add --bootstrap-server and --command-config options for new AdminClient. Update ConfigCommand to use new AdminClient for dynamic broker config updates in KIP-226. Full conversion of ConfigCommand to new AdminClient will be done later under KIP-248.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)