kbuci opened a new pull request, #18093: URL: https://github.com/apache/hudi/pull/18093
…back plan if exception is thrown while reading it ### Describe the issue this Pull Request addresses When using multi-writer mode, if an exception is thrown while reading a pending rollback plan, the corrupted rollback plan should NOT be deleted. Previously, corrupted rollback plans were always deleted regardless of concurrency mode, which could cause issues in multi-writer scenarios where another writer may be currently executing said plan. See https://github.com/apache/hudi/issues/17922 ### Summary and Changelog **Summary:** In multi-writer mode, corrupted rollback plans are now preserved (skipped rather than deleted) when an exception occurs while reading them. Single-writer mode continues to delete corrupted rollback plans. **Changelog:** - Modified `BaseHoodieTableServiceClient.getPendingRollbackInfos()` to only delete corrupted rollback plans (if an exception was encountered when trying to read it) when NOT using multi-writer mode ### Impact - **Behavioral change:** In multi-writer mode, corrupted pending rollback plans will remain on the timeline instead of being deleted - **No public API changes** - **Improved multi-writer safety:** Prevents one writer from deleting a rollback plan that another concurrent writer may depend on ### Risk Level **Low** - The change only affects error handling behavior for multi-writer mode. Single-writer behavior is unchanged ### Documentation Update None - This is an internal behavioral fix with no new configs or user-facing feature changes. ### Contributor's checklist - [ ] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [ ] Enough context is provided in the sections above - [ ] Adequate tests were added if applicable -- 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]
