[
https://issues.apache.org/jira/browse/KAFKA-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986098#comment-14986098
]
ASF GitHub Bot commented on KAFKA-2707:
---------------------------------------
GitHub user ymatsuda opened a pull request:
https://github.com/apache/kafka/pull/408
KAFKA-2707: make KStream processor names deterministic
@guozhangwang
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ymatsuda/kafka kstream_processor_name
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/408.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #408
----
commit 4d26184b26fcf50633f26081d10748ce6db94f65
Author: Yasuhiro Matsuda <yasuh...@confluent.io>
Date: 2015-10-30T16:55:52Z
kstream processor name
commit 9265d24ec7538052bc60fd51d7aa18f6cb7d6b66
Author: Yasuhiro Matsuda <yasuh...@confluent.io>
Date: 2015-11-02T21:31:39Z
Merge branch 'trunk' of github.com:apache/kafka into kstream_processor_name
----
> Make KStream processor names deterministic
> ------------------------------------------
>
> Key: KAFKA-2707
> URL: https://issues.apache.org/jira/browse/KAFKA-2707
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Yasuhiro Matsuda
>
> Currently KStream processor names are generated from AtomicInteger static
> member of KStreamImpl. It is incremented every time a new processor is
> created. The problem is the name depends on the usage history of its use in
> the same JVM, thus the corresponding processors may have different names in
> different processes. It makes it difficult to debug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
