[
https://issues.apache.org/jira/browse/KAFKA-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406832#comment-16406832
]
Matthias J. Sax edited comment on KAFKA-6692 at 3/20/18 6:29 PM:
-----------------------------------------------------------------
The prefix of those topics is the user specified {{application.id}} that is
passed in as a config. Thus, users can also add a "{{__}}"-prefix to the
application ID to get the same naming pattern.
was (Author: mjsax):
The prefix of those topics is the user specified {{application.id}} that is
passed in as a config. Thus, users can also add the {{__}} to the application
ID to get the same naming pattern.
> 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)
