[ https://issues.apache.org/jira/browse/KAFKA-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406777#comment-16406777 ]
Matthias J. Sax edited comment on KAFKA-6692 at 3/20/18 6:03 PM: ----------------------------------------------------------------- All internal topics are prefixed with the user specified {{application.id}}. It's {{"<application.id>-<someName>-repartition"}} and {{"<application.id>-<someName>-changelog"}}. I am wondering it this is sufficient or not? What does adding two underscored improve? (Sorry, the mark up is terrible... can get rid or "dash" triggering strikethough) was (Author: mjsax): All internal topics are prefixed with the user specified {{application.id}}. It's {{"<application.id>--<someName>-repartition"-}} and {{"<application.id>-<someName>-changelog"}}. I am wondering it this is sufficient or not? What does adding two underscored improve? (Sorry, the mark up is terrible... can get rid or "dash" triggering strikethough) > Kafka Streams internal topics should be prefixed with an underscore > ------------------------------------------------------------------- > > Key: KAFKA-6692 > URL: https://issues.apache.org/jira/browse/KAFKA-6692 > Project: Kafka > Issue Type: Improvement > Components: streams > Affects Versions: 1.0.0 > Reporter: Yeva Byzek > Priority: Major > > Issue: users cannot quickly/easily differentiate between their explicitly > created topics from internal topics that Kafka Streams uses, e.g. > {{*-changelog}} and {{*-repartition}} > > Proposed solution: Kafka Streams internal topics should be prefixed with an > underscore > Value add: ability to introspect kstreams and be able to *know* a set of > topics are associated with a topology. This can help downstream tooling to > do cool visualizations and tracking -- This message was sent by Atlassian JIRA (v7.6.3#76005)