You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Clément MATHIEU (Jira)" <ji...@apache.org> on 2020/12/08 09:39:00 UTC

[jira] [Commented] (KAFKA-5386) [Kafka Streams] - custom name for state-store change-log topic

    [ https://issues.apache.org/jira/browse/KAFKA-5386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17245770#comment-17245770 ] 

Clément MATHIEU commented on KAFKA-5386:
----------------------------------------

It is unclear to me how KIP-182 solves this issue. 

My understanding is that ProcessorStateManager.storeChangelogTopic still decides of the topic name and applications cannot provide an override. Am I missing something?



> [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
>            Priority: Major
>              Labels: needs-kip
>             Fix For: 1.0.0
>
>
> 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
(v8.3.4#803005)