You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2017/11/13 20:45:00 UTC
[jira] [Updated] (KAFKA-4857) Replace StreamsKafkaClient with
AdminClient in Kafka Streams
[ https://issues.apache.org/jira/browse/KAFKA-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guozhang Wang updated KAFKA-4857:
---------------------------------
Summary: Replace StreamsKafkaClient with AdminClient in Kafka Streams (was: Use AdminClient in Kafka Streams)
> Replace StreamsKafkaClient with AdminClient in Kafka Streams
> ------------------------------------------------------------
>
> Key: KAFKA-4857
> URL: https://issues.apache.org/jira/browse/KAFKA-4857
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Matthias J. Sax
> Assignee: Matthias J. Sax
> Labels: needs-kip
>
> 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.
> As this is a public API change, a KIP is required.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)