You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Roman Khachatryan (Jira)" <ji...@apache.org> on 2022/07/14 09:47:00 UTC
[jira] [Assigned] (FLINK-26853) HeapStateBackend ignores metadata updates in certain cases
[ https://issues.apache.org/jira/browse/FLINK-26853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Khachatryan reassigned FLINK-26853:
-----------------------------------------
Assignee: Hangxiang Yu
> HeapStateBackend ignores metadata updates in certain cases
> ----------------------------------------------------------
>
> Key: FLINK-26853
> URL: https://issues.apache.org/jira/browse/FLINK-26853
> Project: Flink
> Issue Type: Bug
> Components: Runtime / State Backends
> Affects Versions: 1.14.4, 1.15.0, 1.16.0
> Reporter: Roman Khachatryan
> Assignee: Hangxiang Yu
> Priority: Minor
> Labels: pull-request-available
>
> On recovery, HeapRestoreOperation reads state handles one by one;
> * each handle contains metadata at the beginning;
> * the metadata is always read, but not actually used if a state with the corresponding name was already registered
> In a rare case of downscaling + multiple checkpoints with different metadata; this might lead to data being deserialized incorrectly (always using the initial metadata).
> It also prevents incremental checkpoints with schema evolution.
> On first access, however, the backend itself will update (merge) metadata; so that it doesn't affect new state updates.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)