You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Jark Wu (JIRA)" <ji...@apache.org> on 2019/07/23 02:12:00 UTC

[jira] [Resolved] (FLINK-13322) Fix serializer snapshot recovery in BaseArray and BaseMap serializers.

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

Jark Wu resolved FLINK-13322.
-----------------------------
    Resolution: Fixed

Fixed in 1.9.0: 56e45c8397bdaf3a8dec45164021c54db5b47e7e

> Fix serializer snapshot recovery in BaseArray and BaseMap serializers.
> ----------------------------------------------------------------------
>
>                 Key: FLINK-13322
>                 URL: https://issues.apache.org/jira/browse/FLINK-13322
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / Runtime
>            Reporter: Caizhi Weng
>            Assignee: Caizhi Weng
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0, 1.10.0
>
>
> In BaseArray and BaseMap serializers, their element (or key/value) serializers are not stored in the config snapshot. When restoring the BaseArray/BaseMap serializers from the snapshots, their element/key/value serializers might be incorrect. This situation will happen when user uses his custom kryo serializers as element/key/value serializers.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)