[
https://issues.apache.org/jira/browse/KAFKA-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849057#comment-15849057
]
Matthias J. Sax commented on KAFKA-4722:
----------------------------------------
How does this relate to multiple KStream / KTables ? A topology is translated
into a set of tasks and a thread can execute multiple tasks. Thus, a single
thread can process multiple KStreams and/or KTables. So what would you gain if
you customize the thread name? You cannot know anyway which thread will process
what task, Furthermore, during processing, tasks can also be migrated from one
thread to another (for example, when you scale out your application).
> StreamThread should allow customization of thread prefix
> --------------------------------------------------------
>
> Key: KAFKA-4722
> URL: https://issues.apache.org/jira/browse/KAFKA-4722
> Project: Kafka
> Issue Type: New Feature
> Components: streams
> Affects Versions: 0.10.1.1
> Reporter: Steven Schlansker
>
> StreamThread currently sets its name thusly:
> {code}
> super("StreamThread-" + STREAM_THREAD_ID_SEQUENCE.getAndIncrement());
> {code}
> When you have multiple KStream / KTables in an application, it would be nice
> to customize the "StreamThread" prefix. The id is a good start but a
> human-recognizable name would make logs much easier to read.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
