[
https://issues.apache.org/jira/browse/FLINK-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042744#comment-16042744
]
ASF GitHub Bot commented on FLINK-6869:
---------------------------------------
Github user StefanRRichter commented on the issue:
https://github.com/apache/flink/pull/4090
Overall, I think this is ok as a best effort until we have some eager
registration that helps with the remaining problems in the heap backend.
> Scala serializers do not have the serialVersionUID specified
> ------------------------------------------------------------
>
> Key: FLINK-6869
> URL: https://issues.apache.org/jira/browse/FLINK-6869
> Project: Flink
> Issue Type: Bug
> Components: Scala API, Type Serialization System
> Affects Versions: 1.3.0
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Tzu-Li (Gordon) Tai
> Priority: Blocker
> Labels: flink-rel-1.3.1-blockers
> Fix For: 1.3.1
>
>
> Currently, all Scala serializers, e.g. {{OptionSerializer}},
> {{CaseClassSerializer}}, {{TrySerializer}} etc. do not have the
> serialVersionUID specified.
> In 1.3, the Scala serializer (all serializers in general) implementations had
> to be changed since implementation of the compatibility methods
> {{snapshotConfiguration}}, {{ensureCompatibility}} had to be implemented,
> resulting in a new serialVersionUID.
> This means that when restoring from a snapshot pre-1.3 that contains Scala
> types as state, the previous serializer in the snapshot cannot be
> deserialized (due to UID mismatch).
> To fix this, we should specify the serialVersionUIDs of the Scala serializers
> to be what they originally were pre-1.3. This would then allow users with
> Scala types as state to restore from older versions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
