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

Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2019/04/01 04:29:00 UTC

[jira] [Closed] (FLINK-12064) RocksDBKeyedStateBackend snapshot uses incorrect key serializer if reconfigure happens during restore

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

Tzu-Li (Gordon) Tai closed FLINK-12064.
---------------------------------------
    Resolution: Fixed

Thanks for the fix [~carp84].

Merged with the following commits:
master (1.9.0) - c5e4accffd47eca269b25970127048258e33cb45
release-1.8 (1.8.0) - 9795457a0228e055b82049977ac84d5bc70e6a23

> RocksDBKeyedStateBackend snapshot uses incorrect key serializer if reconfigure happens during restore
> -----------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-12064
>                 URL: https://issues.apache.org/jira/browse/FLINK-12064
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Yu Li
>            Assignee: Yu Li
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.8.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> As titled, in current {{RocksDBKeyedStateBackend}} we use {{keySerializer}} rather than {{keySerializerProvider.currentSchemaSerializer()}}, which is incorrect. The issue is not revealed in existing UT since current cases didn't check snapshot after state schema migration.
> This is a regression issue caused by the FLINK-10043 refactoring work.



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