[
https://issues.apache.org/jira/browse/KAFKA-13588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jose Armando Garcia Sancio updated KAFKA-13588:
-----------------------------------------------
Description:
[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.
was:
[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.3.0
Or any other place that we generate an internal topic name.
> 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)
