Table of Contents |
---|
Status
Current state: Under DiscussionAccepted (vote thread)
Discussion thread: here (and the original discussion is here)
JIRA:
Jira | ||||||
---|---|---|---|---|---|---|
|
Released: 2.2
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Motivation
Currently kafka-topics.sh
uses only direct Zookeeper connections which is not really desired compared to the AdminClient. This change would aim to add capability to the TopicCommand to be able to connect to a broker using the AdminClient.
...
- Allows clients in any language to administrate Kafka (Wire protocol is supported by any language)
- Provides public client for performing admin operations
- Ensures integration test code in other projects and clients maintains compatibility
- Prevents users from needing to use the Command classes and work around standard output and system exits
- Removing the need for admin scripts (
kafka-configs.sh
,kafka-topics.sh
, etc) to talk directly to Zookeeper. - Allows ZNodes to be completely locked down via ACLs
- Further hides the Zookeeper details of Kafka
...
The change proposed in this KIP is to add an extra option as stated above and to migrate create, delete, list and describe operations to use a broker connection. This would be a backward compatible change, meaning leaving the zookeeper option would be still available and fully working until a further point in time but hopefully would but would deprecate it as part of this KIP.
...
This KIP won't implement topic config alternation as that is deprecated in the TopicCommand and should be done by kafka-configs.sh
. The only alternation we allow is changing the partition number for topics.
...
Also retrieving the list of topics that are marked for deletion won't be implemented now as currently it's not possible to retrieve via any protocols. This conversation is part of KIP-142. The implementation will add a note regarding this in its output.
As part of the --zookeeper
option deprecation we will mark it as deprecated in the command help but also print out a warning message about using this deprecated option.
Test Plan
The existing tests will be run with the --bootstrap-server
mode too. Additionally we can refactor some of the kafka-topics.sh
usages in the smokes to use the AdminClient mode.
...