flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tzu-Li (Gordon) Tai (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-6554) CompatibilityResult should contain a notCompatible() option
Date Sat, 13 May 2017 09:12:04 GMT

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

Tzu-Li (Gordon) Tai resolved FLINK-6554.
       Resolution: Fixed
    Fix Version/s: 1.4.0

Fixed for master via 947c44e862396baa95e74cbdc50a4c7cd3befe9b.
Fixed for 1.3 via 4eebf21e9e97719d2a14e8530dcea361de384d64.

> CompatibilityResult should contain a notCompatible() option
> -----------------------------------------------------------
>                 Key: FLINK-6554
>                 URL: https://issues.apache.org/jira/browse/FLINK-6554
>             Project: Flink
>          Issue Type: Improvement
>          Components: Type Serialization System
>    Affects Versions: 1.3.0, 1.4.0
>            Reporter: Chesnay Schepler
>            Assignee: Tzu-Li (Gordon) Tai
>            Priority: Minor
>             Fix For: 1.3.0, 1.4.0
> The {{CompatibilityResult}} allows a {{TypeSerializer}} to specify whether it is compatible
based on the given {{TypeSerializerConfigSnapshot}}.
> As it stands the only options are {{compatible}} and {{requiresMigration}}. We should
allow serializers to also notify the system of an incompatibility which should then fail the
> This would for example be required when a serializer provides an upgrade path version1
-> version2 -> version3, but not directly from version1 -> version3. Currently, the
serializer would either have to contain logic to upgrade from every single previous version
or simply throw an exception on it's own.

This message was sent by Atlassian JIRA

View raw message