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 2018/11/06 06:41:00 UTC
[jira] [Updated] (FLINK-10789) Some new serializer snapshots added
after 1.6 are not implementing the new TypeSerializerSnapshot interface
[ https://issues.apache.org/jira/browse/FLINK-10789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-10789:
-----------------------------------
Labels: pull-request-available (was: )
> Some new serializer snapshots added after 1.6 are not implementing the new TypeSerializerSnapshot interface
> -----------------------------------------------------------------------------------------------------------
>
> Key: FLINK-10789
> URL: https://issues.apache.org/jira/browse/FLINK-10789
> Project: Flink
> Issue Type: Improvement
> Components: Type Serialization System
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Tzu-Li (Gordon) Tai
> Priority: Critical
> Labels: pull-request-available
>
> In commit [3787b89105c6a005ddca999b0b8a0356e812ede6|[https://github.com/apache/flink/commit/3787b89105c6a005ddca999b0b8a0356e812ede6],] there were a few serializer snapshot implementations that were newly added, namely:
> - {{LockableSerializerConfigSnapshot}}
> - {{ListViewSerializerConfigSnapshot}}
> - {{MapViewSerializerConfigSnapshot}}
> - {{ScalaEitherSerializerConfigSnapshot}}
> The problem is that instead of implementing the newer {{TypeSerializerSnapshot}}, they are extending the legacy deprecated {{TypeSerializerConfigSnapshot}}. This doesn't break things, but we will be redundantly writing Java-serialized with the new snapshots, as well as causing us to must introduce migration paths code later on after releasing them.
> It would be more ideal to implement them properly as {{TypeSerializerSnapshot}} for the release.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)