You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (Jira)" <ji...@apache.org> on 2020/05/17 10:37:00 UTC

[jira] [Updated] (FLINK-17520) Extend CompositeTypeSerializerSnapshot to allow composite serializers to signal migration based on outer configuration

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

Timo Walther updated FLINK-17520:
---------------------------------
    Priority: Critical  (was: Major)

> 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
>
> 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)