Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
When org.apache.hudi.spark3.internal.HoodieDataSourceInternalBatchWrite#abort is called, all the subtasks may not have already been canceled. So if we rollback current instant immediately, there may be new files been written after rollback scheduled, which will cause dirty data.
We should rollback the failed instant using common mechanism eager and lazy
Attachments
Issue Links
- links to