[jira] [Closed] (FLINK-11755) Remove ensureCompatibility method from TypeSerializer abstraction

["Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org>]

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

Tzu-Li (Gordon) Tai closed FLINK-11755.
---------------------------------------
      Resolution: Fixed
    Release Note: 
The {{ensureCompatibility}} method have been removed from {{TypeSerializer}}. All other related classes, such as {{CompatibilityResult}}, has also been removed.
Please refer to the class-level Javadoc of {{TypeSerializer}} for instructions on how you should update your serializer implementations to adapt to the new serialization compatibility abstractions {{TypeSerializerSnapshot}} and {{TypeSerializerSchemaCompatibility}}.

Merged.

1.8.0: ae6249789c8aac67f6fd9bde05c1f45e64dd7afa
1.9.0: 572b9d6250b8bcdd5d9968ab12a223a3daf762f1

> Remove ensureCompatibility method from TypeSerializer abstraction
> -----------------------------------------------------------------
>
>                 Key: FLINK-11755
>                 URL: https://issues.apache.org/jira/browse/FLINK-11755
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / Type Serialization System
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Tzu-Li (Gordon) Tai
>            Priority: Blocker
>             Fix For: 1.8.0
>
>
> With {{TypeSerializer#canEqual}} removed in 1.8.0 and the interface already broken for backwards compatibility, it would make sense to also remove the {{ensureCompatibility}} method.
> This method was already deprecated for a whole major version (since 1.7.0) already.
> The effect of removing this method completely:
> - All restored legacy {{TypeSerializerConfigSnapshot}}'s compatibility checks would not be able to go through {{ensureCompatibility}}. Instead, they must be redirected to new snapshot classes that implement {{TypeSerializerSnapshot}}.
> - If the user already upgraded to the {{TypeSerializerSnapshot}} interface in 1.7.x, then this wouldn't be a concern. This only affects users who are still on the {{TypeSerializerConfigSnapshot}} interface.



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