hudi-bot opened a new issue, #15330: URL: https://github.com/apache/hudi/issues/15330
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. ## JIRA info - Link: https://issues.apache.org/jira/browse/HUDI-4599 - Type: Improvement -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
