You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/01/22 16:58:00 UTC

[jira] [Updated] (FLINK-11406) Return TypeSerializerSchemaCompatibility.incompatible() when arity of nested serializers don't match in CompositeTypeSerializerSnapshot's compatibility check

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

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

> Return TypeSerializerSchemaCompatibility.incompatible() when arity of nested serializers don't match in CompositeTypeSerializerSnapshot's compatibility check
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-11406
>                 URL: https://issues.apache.org/jira/browse/FLINK-11406
>             Project: Flink
>          Issue Type: Improvement
>          Components: Type Serialization System
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Tzu-Li (Gordon) Tai
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.8.0
>
>
> Right now, in {{CompositeTypeSerializerSnapshot.resolveSchemaCompatibility(...)}}, if arity of nested serializers don't match between the snapshot and the provided new serializer, a runtime exception is thrown.
> More ideally, this should return {{TypeSerializerSchemaCompatibility.incompatible()}}.
> We should also make it more clearer in the Javadocs that the {{CompositeTypeSerializerSnapshot}} is intended for product serializers that have a fixed arity of nested serializers.



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