[jira] [Updated] (FLINK-28582) LSM tree structure may be incorrect when multiple jobs are committing into the same bucket

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

> LSM tree structure may be incorrect when multiple jobs are committing into the same bucket
> ------------------------------------------------------------------------------------------
>
>                 Key: FLINK-28582
>                 URL: https://issues.apache.org/jira/browse/FLINK-28582
>             Project: Flink
>          Issue Type: Bug
>          Components: Table Store
>    Affects Versions: table-store-0.2.0
>            Reporter: Caizhi Weng
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: table-store-0.2.0
>
>
> Currently `FileStoreCommitImpl` only checks for conflicts by checking the files we're going to delete (due to compaction) are still there.
> However, consider two jobs committing into the same LSM tree at the same time. For their first compaction no conflict is detected because they'll only delete their own level 0 files. But they will both produce level 1 files and the key ranges of these files may overlap. This is not correct for our LSM tree structure.



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