Critical Description
While working on HUDI-3322, i've spotted following contraption:
When we are rolling back Delta Commits, we add corresponding ROLLBACK_PREVIOUS_BLOCK Command Block at the back of the "queue". When we restore, we issue a sequence of Rollbacks, which means that stack if such Rollback Blocks could be of size > 1.
However, when reading that MOR table if the reader does not specify `readBlocksLazily=true`, we'd be merging Blocks eagerly (when instants increment) therefore essentially rendering such Rollback Blocks useless since they can't "unmerge" previously merged records, resurrecting the data that was supposed to be rolled back.
Attachments
Issue Links
- Discovered while testing
-
HUDI-3322 Rollback Plan for Delta Commits constructed incorrectly
-
- Closed
-