You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2018/03/20 18:08:00 UTC
[jira] [Issue Comment Deleted] (KAFKA-6692) Kafka Streams internal
topics should be prefixed with an underscore
[ https://issues.apache.org/jira/browse/KAFKA-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias J. Sax updated KAFKA-6692:
-----------------------------------
Comment: was deleted
(was: All internal topics are prefixed with the user specified {{application.id}}. It's {{"<application.id>DASH<someName>-repartition"}} and {{"<application.id>DASH<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)