We should support a new state .abort so that the commits and table service instants can be cancelled on the timeline (right now after clustering is scheduled, it cannot be cancelled). In this way, we can filter out such instants without having to do rollbacks. This ticket also involves making the new state .abort used by all writers and readers wrt timeline and FileSystem view so it works end-to-end.
JIRA info
Comments
12/Sep/24 01:53;guoyihua;[~shivnarayan] is going to propose the high-level design first before we go with the implementation.;;;
03/Oct/24 01:41;shivnarayan;Please check https://issues.apache.org/jira/browse/HUDI-8291
for more details. ;;;
We should support a new state
.abortso that the commits and table service instants can be cancelled on the timeline (right now after clustering is scheduled, it cannot be cancelled). In this way, we can filter out such instants without having to do rollbacks. This ticket also involves making the new state.abortused by all writers and readers wrt timeline and FileSystem view so it works end-to-end.JIRA info
Comments
12/Sep/24 01:53;guoyihua;[~shivnarayan] is going to propose the high-level design first before we go with the implementation.;;;
03/Oct/24 01:41;shivnarayan;Please check https://issues.apache.org/jira/browse/HUDI-8291
for more details. ;;;