[
https://issues.apache.org/jira/browse/KAFKA-10179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140208#comment-17140208
]
Matthias J. Sax commented on KAFKA-10179:
-----------------------------------------
What you say is fair I guess. Given the current code, if you want to do any of
those, you need to disable the optimization.
However, for the actual bug this ticket is about, the problem seems to be, that
if the optimization is turned on, at some point in the code we pass the
changelog topic name into the serde instead of the source topic name. And thus
the schema cannot be found and the serde crashes. Thus, this ticket should
focus on this bug.
Not sure if KAFKA-8037 covers all cases you describe. Maybe you want to follow
up on this ticket (so we can extent its scope) or create a new ticket that
describes the shortcomings of the current implementation.
> State Store Passes Wrong Changelog Topic to Serde for Optimized Source Tables
> -----------------------------------------------------------------------------
>
> Key: KAFKA-10179
> URL: https://issues.apache.org/jira/browse/KAFKA-10179
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 2.5.0
> Reporter: Bruno Cadonna
> Assignee: Bruno Cadonna
> Priority: Major
> Fix For: 2.7.0
>
>
> {{MeteredKeyValueStore}} passes the name of the changelog topic of the state
> store to the state store serdes. Currently, it always passes {{<application
> ID>-<store name>-changelog}} as the changelog topic name. However, for
> optimized source tables the changelog topic is the source topic.
> Most serdes do not use the topic name passed to them. However, if the serdes
> actually use the topic name for (de)serialization, e.g., when Kafka Streams
> is used with Confluent's Schema Registry, a
> {{org.apache.kafka.common.errors.SerializationException}} is thrown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
