[
https://issues.apache.org/jira/browse/HUDI-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Guo updated HUDI-4599:
----------------------------
Description: In case of misconfiguration or unintended deployment model,
where multiple writers write to the same table without concurrency control, the
writer should be able to detect that through what's on the storage, e.g., the
Hudi timeline, and abort the commit. If we can enforce a pre-commit check
leveraging the timeline (in single-writer case, there should not be new
complete/inflight commits this writer is unaware of), an accidental
multi-writer case should fail one writer and prevent the table from corrupted.
> Add single-writer validation if concurrency control is not enabled
> ------------------------------------------------------------------
>
> Key: HUDI-4599
> URL: https://issues.apache.org/jira/browse/HUDI-4599
> Project: Apache Hudi
> Issue Type: Improvement
> Reporter: Ethan Guo
> Priority: Major
> Fix For: 0.13.0
>
>
> In case of misconfiguration or unintended deployment model, where multiple
> writers write to the same table without concurrency control, the writer
> should be able to detect that through what's on the storage, e.g., the Hudi
> timeline, and abort the commit. If we can enforce a pre-commit check
> leveraging the timeline (in single-writer case, there should not be new
> complete/inflight commits this writer is unaware of), an accidental
> multi-writer case should fail one writer and prevent the table from corrupted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
