Re: [I] Introduce a `.abort` state for abandoned commits and table services [hudi]

["rangareddy (via GitHub)" <gi...@apache.org>]

rangareddy commented on issue #16609:
URL: https://github.com/apache/hudi/issues/16609#issuecomment-5434690270

   This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-8189).
   
   **Findings: not implemented on `master`.**
   
   `hudi-common/src/main/java/org/apache/hudi/common/table/timeline/HoodieInstant.java` contains no `ABORT` state, so a scheduled clustering plan still cannot be cancelled without going through a rollback - exactly as the description says.
   
   One thing worth recording on the ticket before this is picked up: introducing a new instant state is a change to the timeline's on-disk state machine, and the body already scopes it as "used by all" commits and table services. That means every reader that filters instants by state has to understand `.abort`, and older readers encountering it need defined behaviour. So this needs a compatibility and table-version story rather than being a local addition - which is probably why it has not moved.
   


-- 
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: commits-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org