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 2022/01/28 14:29:00 UTC

[jira] [Updated] (FLINK-25492) Changelog with InMemoryStateChangelogStorage cannot work well

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

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

> Changelog with InMemoryStateChangelogStorage cannot work well
> -------------------------------------------------------------
>
>                 Key: FLINK-25492
>                 URL: https://issues.apache.org/jira/browse/FLINK-25492
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / State Backends
>            Reporter: Hangxiang Yu
>            Assignee: Hangxiang Yu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>         Attachments: changelog_in-memory_storage_bug.patch
>
>
> while using ChangelogStataBackend with InMemoryStateChangelogStorage, the seq will be increased when append a record. The materialization will materilalize the record into delegated state backend. But after the materialization finished, the persist method still puts the record into InMemoryChangelogStateHandle which is incorrect.
> Just as the patch shows, ChangelogDelegateHashMapInMemoryTest will fail because when restore, the medata cannot be found and the record that should't be there is restored firstly.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)