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

Tzu-Li (Gordon) Tai closed FLINK-17520.
---------------------------------------
    Fix Version/s: 1.12.0
     Release Note: The `boolean isOuterSnapshotCompatible(TypeSerializer)` on 
the `CompositeTypeSerializerSnapshot` class has been deprecated, in favor of a 
new `OuterSchemaCompatibility resolveOuterSchemaCompatibility(TypeSerializer)` 
method. Please implement that instead. Compared to the old method, the new 
method allows composite serializers to signal state schema migration based on 
outer schema and configuration.
       Resolution: Fixed

master - 87e92ddabb8067dc16e2a0fb59ede14d7fbaee74
release-1.11 - 91a4c2af08fb874ecd264c8af36709c6a340009d

> Extend CompositeTypeSerializerSnapshot to allow composite serializers to 
> signal migration based on outer configuration
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-17520
>                 URL: https://issues.apache.org/jira/browse/FLINK-17520
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / Type Serialization System
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Tzu-Li (Gordon) Tai
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.11.0, 1.12.0
>
>
> Compatibility of composite serializers is governed by the overall resolved 
> compatibility of all its nested serializers, as well as any additional 
> configuration (or what we call the "outer configuration" or "outer snapshot").
> The compatibility resolution logic for these composite serializers is 
> implemented in the {{CompositeTypeSerializerSnapshot}} abstract class.
> One current limitation of this base class is that the implementation assumes 
> that the outer configuration is always either compatible, or incompatible.
> We should relax this to also allow signaling migration, purely based on the 
> outer configuration. This is already a requirement by FLINK-16998.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to