Kafka’s administrative API performs cluster-resource operations programmatically. The preferred type is the Admin interface; the abstract AdminClient class is discouraged and may be removed in a future release. section 4.1 section 4.5
Use it to inspect topics, brokers, ACLs, and configuration, or to create, list, delete, describe, and modify topics and records. Topic management is especially useful for testing and prototyping, while production broker administration commonly remains an operations responsibility. section 4.5
A typical administrative workflow is:
- Resolve ListTopicResult.names() through KafkaFuture.get(), which blocks until the request completes. section 4.5
Create and remove development topics
Configure localhost:9092, create an Admin client, add topic-one and topic-two as single-partition, single-replica topics, list their names, and delete topic-two. Run destructive operations cautiously in shared environments. section 4.5
