[
https://issues.apache.org/jira/browse/KAFKA-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747588#comment-16747588
]
Guozhang Wang commented on KAFKA-6964:
--------------------------------------
This is part of the reason. The more larger scoped context is:
1. We are allowing users to indicate processor names / state store names for
stateful operations via controlled object and KIP-307. Hence for users who
would like to have customized internal names for smooth upgrade etc, they can
do that already. Much of the related discussions happened on that ticket.
2. As for security, ACLs will be able to be set via kafka-acls command lines
which will translate into internal topics etc.
With these two in mind, I think we can close this JIRA now to not expose
internal topics, but tackle it in the reversed ordering: allow users to
customize their internal topics via public APIs.
> Add ability to print all internal topic names
> ---------------------------------------------
>
> Key: KAFKA-6964
> URL: https://issues.apache.org/jira/browse/KAFKA-6964
> Project: Kafka
> Issue Type: New Feature
> Components: streams
> Reporter: Bill Bejeck
> Assignee: Jagadesh Adireddi
> Priority: Major
> Labels: needs-kip
>
> For security access reasons some streams users need to build all internal
> topics before deploying their streams application. While it's possible to
> get all internal topic names from the {{Topology#describe()}} method, it
> would be nice to have a separate method that prints out only the internal
> topic names to ease the process.
> I think this change will require a KIP, so I've added the appropriate label.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
