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] [Updated] (FLINK-10679) Let TypeSerializerSchemaCompatibility.resolveSchemaCompatibility() be the entry point for compatibility checks in framework code
Date Thu, 25 Oct 2018 16:33:00 GMT

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

ASF GitHub Bot updated FLINK-10679:
-----------------------------------
    Labels: pull-request-available  (was: )

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

Mime
View raw message