[
https://issues.apache.org/jira/browse/KAFKA-5386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091463#comment-16091463
]
Bart Vercammen edited comment on KAFKA-5386 at 7/18/17 12:01 PM:
-----------------------------------------------------------------
Actually this is going to be a little harder than initially expected, as the
KStream API can create a bunch of _repartition_ topics under the hood, that I
also wish to comply to a certain known naming convention.
Basically what I'm trying to achieve is that every kafka-topic that is going to
be created is known up front, and that it complies to a certain naming
strategy. It would be nice if this naming strategy could be configured somehow.
Any suggestions on this?
was (Author: cloutrix):
Actually this is going to be a little harder than initially expected, as the
KStreams API can create a bunch of _repartition_ topics under the hood, that I
also wish to comply to a certain known naming convention.
Basically what I'm trying to achieve is that every kafka-topic that is going to
be created is known up front, and that it complies to a certain naming
strategy. It would be nice if this naming strategy could be configured somehow.
Any suggestions on this?
> [Kafka Streams] - custom name for state-store change-log topic
> --------------------------------------------------------------
>
> Key: KAFKA-5386
> URL: https://issues.apache.org/jira/browse/KAFKA-5386
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 0.10.2.1
> Reporter: Bart Vercammen
>
> Currently, when working with Kafka backed state stores in Kafka Streams,
> these log compacted topics are given a hardcoded name :
> _my.app.id-storename-changelog_
> {noformat} public static String storeChangelogTopic(String applicationId,
> String storeName) {
> return applicationId + "-" + storeName + STATE_CHANGELOG_TOPIC_SUFFIX;
> }{noformat}
> It would be nice if somehow I would be able to override this functionality
> and provide the topic-name myself when creating the state-store.
> Any comments?
> Would it be OK to submit a PR for this?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
