prashantwason opened a new pull request, #18033:
URL: https://github.com/apache/hudi/pull/18033

   ### Describe the issue this Pull Request addresses
   
   When a pending commit exists on the data table timeline and the metadata 
table folder has been deleted, 
   ingestion continuously fails because the metadata table cannot be 
bootstrapped. This fix allows the 
   metadata table to be bootstrapped if the pending commits are being rolled 
back.
   
   issue: HUDI-2399
   
   ### Summary and Changelog
   
   **Summary:** Allow metadata table initialization to proceed when pending 
data instants are being rolled back.
   
   **Changelog:**
   - Modified 
`HoodieBackedTableMetadataWriterTableVersionSix.shouldInitializeFromFilesystem()`
 to check for pending rollback instants
   - If all blocking pending data instants have corresponding pending rollback 
instants, allow the metadata table bootstrap to proceed
   - Added informational logging when initialization is allowed due to pending 
rollbacks
   
   ### Impact
   
   No public API changes. This fix improves the resilience of the metadata 
table bootstrap process by allowing 
   it to proceed when pending commits are being rolled back, preventing 
continuous ingestion failures.
   
   ### Risk Level
   
   low - The change only relaxes the blocking condition for metadata table 
initialization in a specific scenario 
   (when pending instants are being rolled back). The existing behavior is 
preserved for all other cases.
   
   ### Documentation Update
   
   none
   
   ### Contributor's checklist
   
   - [x] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] 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]

Reply via email to