[
https://issues.apache.org/jira/browse/KAFKA-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375140#comment-15375140
]
ASF GitHub Bot commented on KAFKA-3858:
---------------------------------------
GitHub user enothereska opened a pull request:
https://github.com/apache/kafka/pull/1619
KAFKA-3858: Basic printing of everything
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/enothereska/kafka KAFKA-3858-print-topology
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1619.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 #1619
----
commit 4152616717118ca585d8f0707fb91b9795dd1efd
Author: Eno Thereska <[email protected]>
Date: 2016-07-13T14:45:58Z
Basic printing of everything
----
> Add functions to print stream topologies
> ----------------------------------------
>
> Key: KAFKA-3858
> URL: https://issues.apache.org/jira/browse/KAFKA-3858
> Project: Kafka
> Issue Type: New Feature
> Components: streams
> Affects Versions: 0.10.1.0
> Reporter: Roger Hoover
> Assignee: Eno Thereska
>
> For debugging and development, it would be very useful to be able to print
> Kafka streams topologies. At a minimum, it would be great to be able to see
> the logical topology including with Kafka topics linked by sub-topologies. I
> think that this information does not depend on partitioning. For more
> detail, it would be great to be able to print the same logical topology but
> also showing number of tasks (an perhaps task ids?). Finally, it would be
> great to show the physical topology after the tasks have been mapped to JVMs
> + threads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)