-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Open
Labels
from-jirapriority:highSignificant impact; potential bugsSignificant impact; potential bugstype:improvementImprovements to existing functionalityImprovements to existing functionality
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.
JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-4599
- Type: Improvement
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
from-jirapriority:highSignificant impact; potential bugsSignificant impact; potential bugstype:improvementImprovements to existing functionalityImprovements to existing functionality