You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2017/05/11 18:23:04 UTC
[jira] [Commented] (FLINK-6554) CompatibilityResult should contain
a notCompatible() option
[ https://issues.apache.org/jira/browse/FLINK-6554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006942#comment-16006942 ]
Stephan Ewen commented on FLINK-6554:
-------------------------------------
+1, incompatibility is always possible and should lead to a graceful failure with a good error message
> 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
> Priority: Minor
>
> 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 job.
> 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
(v6.3.15#6346)