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 2025/04/03 03:54:00 UTC

[jira] [Updated] (FLINK-37524) State Serializer in ForState should restore from oldStateInfo in Checkpoint

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

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

> State Serializer in ForState should restore from oldStateInfo in Checkpoint
> ---------------------------------------------------------------------------
>
>                 Key: FLINK-37524
>                 URL: https://issues.apache.org/jira/browse/FLINK-37524
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / State Backends
>    Affects Versions: 2.0.0
>            Reporter: Yue Ma
>            Assignee: Yue Ma
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.1.0
>
>
> Currently, when creating using ForStKeyedStateBackend create a new State , *_AbstractKeyedState_* will directly use the serializer in _*StateDescriptor*_ regardless of whether it is restored from a Checkpoint.
> However, this may cause data to be unable to be restored when the last serializer changes (for example, the class registration order in *_KryoSerializer_* has changed, for specific cases, please refer to {*}_StateBackendTestBase#testKryoRestoreResilienceWithDifferentRegistrationOrder_{*}). Therefore, when creating a State from a Checkpoint, oldStateInfo should be used as the new State's Serializer.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)