[
https://issues.apache.org/jira/browse/KAFKA-6494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347856#comment-16347856
]
ASF GitHub Bot commented on KAFKA-6494:
---------------------------------------
rajinisivaram opened a new pull request #4503: KAFKA-6494; ConfigCommand update
to use AdminClient for broker configs
URL: https://github.com/apache/kafka/pull/4503
Use new AdminClient for describing and altering broker configs using
ConfigCommand. Broker quota configs as well as other configs will continue to
be processed directly using ZooKeeper until KIP-248 is implemented.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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)
