You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yanfei Lei (Jira)" <ji...@apache.org> on 2025/05/11 11:18:00 UTC

[jira] [Assigned] (FLINK-37552) Made StateMetaInfo consistent for ForStKeyeStateBackend and ForStSyncKeyeStateBackend.

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

Yanfei Lei reassigned FLINK-37552:
----------------------------------

    Assignee: Yue Ma  (was: Yanfei Lei)

> Made StateMetaInfo consistent for ForStKeyeStateBackend and ForStSyncKeyeStateBackend.
> --------------------------------------------------------------------------------------
>
>                 Key: FLINK-37552
>                 URL: https://issues.apache.org/jira/browse/FLINK-37552
>             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, if MapState or ListState is used, the StateMeta information saved by ForStKeyeStateBackend and ForStSyncKeyeStateBackend when making cp may be inconsistent, which may cause incompatible states. For example, when using MapState, ForStKeyeStateBackend will save the ValueSerializer information in StateMeta, but ForStSyncKeyeStateBackend will save the MapSerializer information. So we need to unify this place and perform a transformation when ForStKeyeStateBackend creates stateMeta



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