You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2017/05/02 15:44:04 UTC
[jira] [Commented] (KAFKA-4857) Improve Client handling
[ https://issues.apache.org/jira/browse/KAFKA-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993127#comment-15993127 ]
Ismael Juma commented on KAFKA-4857:
------------------------------------
There are 2 changes here. One is to use AdminClient, which doesn't require a KIP. The second is to update KafkaClientSupplier to include a method for the AdminClient. That does require a tiny KIP. We may do both at the same time, but it's not strictly required.
> Improve Client handling
> -----------------------
>
> 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.3.15#6346)