[
https://issues.apache.org/jira/browse/KAFKA-10179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161423#comment-17161423
]
Guozhang Wang commented on KAFKA-10179:
---------------------------------------
I agree with Almog and Rohan’s arguments here. What I’m thinking is how we
could define a principle for users to indicate that:
1) the bytes in the source topic are exactly the same as bytes in the state
store (i.e. the serdes are symmetric).
2) there’s no side-effects that serde incurs; only 1) and 2) together means it
is safe to skip serde during restoration.
3) and also, there’s no corrupted or ill-formatted data from source topics that
should be skipped when loading into state stores. This is
https://issues.apache.org/jira/browse/KAFKA-8037
During restoration time, compared with during normal processing time.
> 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)
