[jira] [Closed] (FLINK-29842) Change commitIdentifier in Table Store snapshot to long value

["Caizhi Weng (Jira)" <ji...@apache.org>]

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

Caizhi Weng closed FLINK-29842.
-------------------------------
    Resolution: Fixed

master: 350627439a70b187f7270278b497841fa3f2c554
release-0.2: bc5646cc62bb341954d6320c7f3ed375195e747f

> Change commitIdentifier in Table Store snapshot to long value
> -------------------------------------------------------------
>
>                 Key: FLINK-29842
>                 URL: https://issues.apache.org/jira/browse/FLINK-29842
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table Store
>    Affects Versions: table-store-0.3.0, table-store-0.2.2
>            Reporter: Caizhi Weng
>            Assignee: Caizhi Weng
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: table-store-0.3.0, table-store-0.2.2
>
>
> Currently {{commitIdentifier}} in {{Snapshot}} is a {{String}} value. However there are many scenarios where we need to compare two identifiers to find out which one is newer. For example
> * In FLINK-29840, we need to store the latest modified commit for each writer. Only when the latest snapshot is newer than this commit can we safely close the writer.
> * In FLINK-29805, we can read the commit identifier of the latest snapshot. All identifiers older than that should be filtered out.
> * In FLINK-29752, we need to trigger full compaction once in a few commits. We can read the latest commit identifier and compare it with the full compaction identifier to check if full compaction is successfully committed.
>  



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