[
https://issues.apache.org/jira/browse/FLINK-10789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tzu-Li (Gordon) Tai closed FLINK-10789.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.7.0
Merged.
1.8.0: d350e9f85d3551368f4f769419e0da8b789ac892
1.7.0: a0720aba4a1ebdb54cf7b713a59f6354b5dd18be
> 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
> Fix For: 1.7.0
>
>
> 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)
