[
https://issues.apache.org/jira/browse/FLINK-12064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16805168#comment-16805168
]
Tzu-Li (Gordon) Tai commented on FLINK-12064:
---------------------------------------------
Just to clarify:
the problem is that the state backend uses the correct key serializer for state
access, but the wrong one is snapshotted in checkpoints, is that correct?
Otherwise, the title implies that it is using the wrong key serializer for
runtime state access.
> 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
>
> Time Spent: 10m
> 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)
