[jira] [Updated] (FLINK-6944) Introduce DefaultTypeSerializerConfigSnapshot as a base implementation for serializer compatibility checks

["Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tzu-Li (Gordon) Tai updated FLINK-6944:
---------------------------------------
    Fix Version/s:     (was: 1.7.0)

> Introduce DefaultTypeSerializerConfigSnapshot as a base implementation for serializer compatibility checks
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-6944
>                 URL: https://issues.apache.org/jira/browse/FLINK-6944
>             Project: Flink
>          Issue Type: Sub-task
>          Components: State Backends, Checkpointing, Type Serialization System
>    Affects Versions: 1.3.0, 1.3.1
>            Reporter: Tzu-Li (Gordon) Tai
>            Priority: Critical
>
> FLINK-9377 proposes to remove writing serializers as part of checkpoint meta info, and only write its configuration snapshot.
> Since then serializer config snapshots will be the single source of truth for previous serializer schema, this JIRA proposes to follow up the change in FLINK-9377 by having a base default implementation for letting {{TypeSerializer.snapshotConfiguration}} that returns a {{DefaultTypeSerializerConfigSnapshot}}.
> The {{DefaultTypeSerializerConfigSnapshot}} should wrap the serialVersionUID of the serializer class, and the serializer class' classname. The latter two will be used to check compatibility in the default implementation of {{TypeSerializer.ensureCompatibility}}. Specifically, if classname / serialVersionUID has changed, the default implementation of {{TypeSerializer.ensureCompatibility}} should return {{CompatibilityResult.requiresMigration}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)