[KAFKA-4857] Replace StreamsKafkaClient with AdminClient in Kafka Streams

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1.0
• Component/s: streams
• Assignee: Matthias J. Sax
• Reporter: Matthias J. Sax
• Created: 06/Mar/17 23:40
• Updated: 08/Dec/17 00:19
• Resolved: 08/Dec/17 00:17

Description

Streams uses KafkaClientSupplier to get consumer/restore-consumer/producer clients. Streams also uses one more client for admin purpose namely StreamsKafkaClient that is instantiated "manually".

With the newly upcoming AdminClient from KIP-117, we can simplify (or even replace StreamsKafkaClient with the new AdminClient. We furthermore want to unify how the client in generated and extend KafkaClientSupplier with method that return this client.

NOTE: The public facing changes are summarized in a separate ticket KAFKA-6170, and this ticket is only for the internal swap, with the accepted criterion to completely remove StreamsKafkaClient with the newly introduced KafkaAdminClient.

Issue Links

• contains: KAFKA-5302 Improve exception handling on streams client (communication with brokers)
• contains: KAFKA-4706 Unify StreamsKafkaClient instances
• contains: KAFKA-6047 Allow retries configuration for InternalTopicManager
• is blocked by: KAFKA-3265 Create Java Admin Client
• is blocked by: KAFKA-6170 Add the AdminClient in Streams' KafkaClientSupplier
• is required by: KAFKA-6124 Revisit default config for internal client with regard to resilience
• links to: GitHub Pull Request #4242