You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Almog Gavra (Jira)" <ji...@apache.org> on 2024/01/02 19:17:00 UTC
[jira] [Commented] (KAFKA-16046) Stream Stream Joins fail after restoration with deserialization exceptions
[ https://issues.apache.org/jira/browse/KAFKA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17801904#comment-17801904 ]
Almog Gavra commented on KAFKA-16046:
-------------------------------------
https://github.com/apache/kafka/pull/15073
> Stream Stream Joins fail after restoration with deserialization exceptions
> --------------------------------------------------------------------------
>
> Key: KAFKA-16046
> URL: https://issues.apache.org/jira/browse/KAFKA-16046
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 3.7.0
> Reporter: Almog Gavra
> Assignee: Almog Gavra
> Priority: Blocker
> Labels: streams
> Fix For: 3.7.0
>
>
> Before KIP-954, the `KStreamImplJoin` class would always create non-timestamped persistent windowed stores. After that KIP, the default was changed to create timestamped stores. This wasn't compatible because, during restoration, timestamped stores have their changelog values transformed to prepend the timestamp to the value. This caused serialization errors when trying to read from the store because the deserializers did not expect the timestamp to be prepended.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)