You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2018/10/31 05:56:00 UTC

[jira] [Closed] (FLINK-10679) Let TypeSerializerSchemaCompatibility.resolveSchemaCompatibility() be the entry point for compatibility checks in framework code

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

Tzu-Li (Gordon) Tai closed FLINK-10679.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.0

Merged for 1.7.0: a567a1ef628eadad21e11864ec328481cd6d7898

> Let TypeSerializerSchemaCompatibility.resolveSchemaCompatibility() be the entry point for compatibility checks in framework code
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-10679
>                 URL: https://issues.apache.org/jira/browse/FLINK-10679
>             Project: Flink
>          Issue Type: Sub-task
>          Components: State Backends, Checkpointing, Type Serialization System
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Stephan Ewen
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.7.0
>
>
> Currently, the state backend framework code still is exposed the now deprecated {{CompatibilityResult}} and relevant classes.
> Instead, all compatibility checks should go through the new {{TypeSerializerSchemaCompatibility#resolveSchemaCompatibility}} method, and allow framework code to check against the more powerful {{TypeSerializerSchemaCompatibility}} for incompatibility / migration requirements.



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