You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/02/02 05:30:00 UTC

[jira] [Commented] (KAFKA-7798) Expose embedded client context from KafkaStreams threadMetadata

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

ASF GitHub Bot commented on KAFKA-7798:
---------------------------------------

mjsax commented on pull request #6107: KAFKA-7798: Expose embedded clientIds
URL: https://github.com/apache/kafka/pull/6107
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Expose embedded client context from KafkaStreams threadMetadata
> ---------------------------------------------------------------
>
>                 Key: KAFKA-7798
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7798
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Guozhang Wang
>            Assignee: Guozhang Wang
>            Priority: Major
>              Labels: kip
>
> A KafkaStreams client today contains multiple embedded clients: producer, consumer and admin client. Currently these client's context like client id are not exposed via KafkaStreams. This ticket proposes to expose those context information at the per-thread basis (since each thread has its own embedded clients) via ThreadMetadata.
> This also has an interplay with KIP-345: as we add group.instance.id in that KIP, this information should also be exposed as well.
> Cf: [https://cwiki.apache.org/confluence/display/KAFKA/KIP-414%3A+Expose+Embedded+ClientIds+in+Kafka+Streams]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)