Does kafka stream provide an API to control how internal topics are named? Right now it uses appId, operator name, etc. In a shared kafka cluster its common to have naming convention that may require some prefix/suffix.
Are you checking to see if you can manually set the internal topic names to follow your own naming convention in your shared cluster? For that the current answer is no, as Streams are trying to abstract users from worrying about them since they are treated as "internals" anyways. But I think it is a faire request moving forward for multi-tenant clusters, and also for allowing different Streams apps to have authorizations to create topics with a different naming patterns, etc.
Guozhang On Fri, Nov 18, 2016 at 1:32 AM, Michael Noll <[EMAIL PROTECTED]> wrote:
Using app id may help to some extent. Will have to think & test this through. Good to know there will be more direct support for this in the future. May be it will play well with KIP-37.
On Fri, Nov 18, 2016 at 1:12 PM, Guozhang Wang <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext