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/03/29 10:37:00 UTC

[jira] [Updated] (FLINK-12064) RocksDBKeyedStateBackend 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 ]

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

> RocksDBKeyedStateBackend 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
>
>
> 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)