You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/01/27 20:02:00 UTC
[jira] [Updated] (FLINK-11436) Java deserialization failure of the
AvroSerializer when used in an old CompositeSerializers
[ https://issues.apache.org/jira/browse/FLINK-11436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-11436:
-----------------------------------
Labels: pull-request-available (was: )
> Java deserialization failure of the AvroSerializer when used in an old CompositeSerializers
> -------------------------------------------------------------------------------------------
>
> Key: FLINK-11436
> URL: https://issues.apache.org/jira/browse/FLINK-11436
> Project: Flink
> Issue Type: Bug
> Components: Type Serialization System
> Affects Versions: 1.7.0, 1.7.1
> Reporter: Igal Shilman
> Assignee: Igal Shilman
> Priority: Major
> Labels: pull-request-available
>
> During the release of Flink 1.7, the value of AvroSerializer, serialVersionUID was uptick to 2L (was 1L before).
> Although the AvroSerializer (along with it's snapshot class) was migrated to the new serialization abstraction (hence free of Java serialization), there were composite serializers that were not yet migrated during that release (i.e. StreamElementSerializer), and were serialized with Java serialization into the checkpoint/savepoint.
> In case that one of the nested serializers were the AvroSerializer we would
> bump into deserialization exception due to a wrong serialVersionUID.
> This issue was initially reported on the user mailing list:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Trouble-migrating-state-from-1-6-3-to-1-7-1-td25694.html
> h3.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)