[
https://issues.apache.org/jira/browse/KAFKA-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091740#comment-17091740
]
Matthias J. Sax commented on KAFKA-9913:
----------------------------------------
Seems a little weird to mix two totally unrelated things into a single KIP?
If you think this ticket is important enough, why not just do a separate KIP? I
would expect the discussion to be rather straight forward and it would not
"district" us from the KIP-598 discussion that may end up a little bit more
tricky.
> TopologyDescription should expose all topic name progrematically
> ----------------------------------------------------------------
>
> Key: KAFKA-9913
> URL: https://issues.apache.org/jira/browse/KAFKA-9913
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Priority: Minor
> Labels: beginner, need-kip, newbie
>
> During the discussion of KIP-594, it became clear that it is helpful for
> testing purpose to verify which topics are used in a topology (ie, all user
> input and output topics, as well as internal topics like repartiton or
> changelog topics).
> While the current `TopologyDescription` does expose this information (only
> changelog topic names are missing atm), there is no convenient way to get all
> topic names at once, but one must traverse the nodes of each sub-topology to
> collect this information manually.
> Hence, the proposal is to add utility methods to `TopologyDescription` that
> expose this information programatically. As this is a public API change, it
> will be required to write a KIP
> ([https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals])
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
