[jira] [Commented] (FLINK-36541) Occasional met commit conflict problem in PaimonSink.

["Leonard Xu (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-36541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897437#comment-17897437 ] 

Leonard Xu commented on FLINK-36541:
------------------------------------

master： f38341b02ed4cfc3c77d28c795e330be2966482e

3.2：TODO

> Occasional met commit conflict problem in PaimonSink.
> -----------------------------------------------------
>
>                 Key: FLINK-36541
>                 URL: https://issues.apache.org/jira/browse/FLINK-36541
>             Project: Flink
>          Issue Type: Improvement
>          Components: Flink CDC
>    Affects Versions: cdc-3.2.0
>            Reporter: Yanquan Lv
>            Assignee: Yanquan Lv
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: cdc-3.3.0, cdc-3.2.1
>
>         Attachments: image-2024-10-15-20-36-03-495.png
>
>
> When writing records to Paimon, we occasional met commit conflict problem even if Parallelism is 1.
> It turns out that PaimonWriter preparecommit Committable with a checkpointId which is always 1, as the following code:
> [https://github.com/apache/flink-cdc/blob/a1781f432d906fa2a864642a5f74ac5bdc963d9c/flink-cdc-connect/flink-cdc-pipeline-connectors/flink-cdc-pipeline-connector-paimon/src/main/java/org/apache/flink/cdc/connectors/paimon/sink/v2/PaimonWriter.java#L164-L178]
> !image-2024-10-15-20-36-03-495.png!
> This is actually an incorrect usage, we must pass in an increasing ID to ensure the correctness of the snapshot information.



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