KIP-4 — Metadata Protocol Changes
Accepted AdminProtocol
Introduces an AdminClient Java API backed by a wire protocol, providing programmatic operations for topic management, ACL management, and configuration changes without requiring direct ZooKeeper access. Prior to this, all administrative operations (kafka-topics.sh, kafka-acls.sh, etc.) wrote directly to ZooKeeper, coupling admin tooling to ZooKeeper connectivity and making multi-language admin clients impractical.
Protocol Impact
Metadata · CreateTopics · DeleteTopics
Details
| Author | Joe Stein |
| Status | Accepted |
| JIRA | KAFKA-1912 |
| Wiki | View on Apache Wiki |
| Created | 2015-01-21 |
| Last Modified | 2017-03-16 |
Explore how this KIP affects the Kafka protocol in the Protocol Explorer, or see the full KIP database.