You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Sharad (JIRA)" <ji...@apache.org> on 2017/06/21 17:10:00 UTC
[jira] [Comment Edited] (KAFKA-4857) Use AdminClient in Kafka
Streams
[ https://issues.apache.org/jira/browse/KAFKA-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16057853#comment-16057853 ]
Sharad edited comment on KAFKA-4857 at 6/21/17 5:09 PM:
--------------------------------------------------------
[~mjsax] Thanks for the clarification.
[~enothereska] I will stick to doing this one only.
was (Author: sharad.develop):
@mjsax Thanks for the clarification.
[~enothereska] I will stick to doing this one 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: Sharad
> 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)