flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-6869) Scala serializers do not have the serialVersionUID specified
Date Tue, 13 Jun 2017 05:19:01 GMT

    [ https://issues.apache.org/jira/browse/FLINK-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047434#comment-16047434

ASF GitHub Bot commented on FLINK-6869:

Github user asfgit closed the pull request at:


> 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

View raw message