You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jose Armando Garcia Sancio (Jira)" <ji...@apache.org> on 2022/08/05 15:05:00 UTC

[jira] [Commented] (KAFKA-13588) We should consolidate `changelogFor` methods to simplify the generation of internal topic names

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

Jose Armando Garcia Sancio commented on KAFKA-13588:
----------------------------------------------------

Moved it to the next release, 3.4.0

> We should consolidate `changelogFor` methods to simplify the generation of internal topic names
> -----------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-13588
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13588
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Walker Carlson
>            Assignee: Guozhang Wang
>            Priority: Minor
>              Labels: newbie
>             Fix For: 3.3.0
>
>
> [https://github.com/apache/kafka/pull/11611#discussion_r772625486]
> we should use `ProcessorContextUtils#changelogFor` after we remove `init(final ProcessorContext context, final StateStore root)` in `CahceingWindowStore#initInternal` — this will happen in around Dec.2022, which is around 3.4.0
>  
> Or any other place that we generate an internal topic name.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)