[
https://issues.apache.org/jira/browse/FLINK-38478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yanquan Lv resolved FLINK-38478.
--------------------------------
Resolution: Fixed
Fixed in master via 6a18cd7f7fe5de9c1a79587f9f0af923f3146fd3.
> There may be a risk of data loss when two jobs write to the same Paimon table
> concurrently
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-38478
> URL: https://issues.apache.org/jira/browse/FLINK-38478
> Project: Flink
> Issue Type: Bug
> Components: Flink CDC
> Affects Versions: cdc-3.1.0, cdc-3.2.0, cdc-3.1.1, cdc-3.3.0, cdc-3.2.1,
> cdc-3.4.0, cdc-3.5.0
> Reporter: Yanquan Lv
> Priority: Blocker
> Labels: pull-request-available
>
> When two jobs write to the same Paimon table concurrently, using the same
> *commit user* and *commit identifier* may result in data loss. Currently, the
> commit user must be explicitly specified in the job.
> To resolve this issue, we can modify the system to automatically generate a
> random *UUID* for each commit, ensuring uniqueness and avoiding conflicts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
