[
https://issues.apache.org/jira/browse/KAFKA-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905380#comment-16905380
]
Bill Bejeck commented on KAFKA-8558:
------------------------------------
[~apurva]
> Bill, where are we with fixing this?
I've started a PR and plan to push it 8/13 - 8/14 timeframe
>Also, if I understand correctly, as trunk stands today, if you upgrade from
>versions < 2.3 to trunk, and if you >name your join node, you will not reuse
>the join state store since the name will have changed?
That's partially correct. In version 2.3 - 2.1, users can name the repartition
topic via `Joined.name`. Right now in trunk if users have named the
repartition topic, the same base name is used for the join operator and state
store (hence changelog topic). With this Jira we'll only re-use the base name
for the repartition topic and join operator and naming of the statestore (and
changelog topic) is done via the Materialized object.
> KIP-479 - Add Materialized Overload to KStream#Join
> ----------------------------------------------------
>
> Key: KAFKA-8558
> URL: https://issues.apache.org/jira/browse/KAFKA-8558
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Bill Bejeck
> Assignee: Bill Bejeck
> Priority: Blocker
> Labels: needs-kip
> Fix For: 2.4.0
>
>
> To prevent a topology incompatibility with the release of 2.4 and the naming
> of Join operations we'll add an overloaded KStream#join method accepting a
> Materialized parameter. This will allow users to explicitly name state stores
> created by Kafka Streams in the join operation.
>
> The overloads will apply to all flavors of KStream#join (inner, left, and
> right).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
