kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guozhang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4857) Use AdminClient in Kafka Streams
Date Mon, 13 Nov 2017 20:45:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16250209#comment-16250209

Guozhang Wang commented on KAFKA-4857:

We have KAFKA-6170 for the KIP-related changes to add AdminClient to public API KafkaClientSupplier.
Modified the title / description of this ticket for internal implementation only.

> Use 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

View raw message