linliu-code opened a new pull request, #12122:
URL: https://github.com/apache/hudi/pull/12122

   ### Change Logs
   
   When we have insert1-delete-insert2 pattern for MOR tables, the log file 
merging would lost the delete records. This causes the merging between the last 
record and the initial record, which should have been removed by the delete 
operation in between. 
   
   To handle this issue, we need a way to record the deletes and avoid merging 
base record and the log record in the end. We utilize the metadata field. 
   When file group reader is enabled, the merger checks if the ordering value 
is stored in the metadata pair.
   When file group reader is disabled, the merger checks if the ordering value 
is stored in the metadata of the log record.
   
   ### Impact
   
   Fixed the inconsistency of delete records for fg reader and non-fg reader.
   
   ### Risk level (write none, low medium or high below)
   
   _If medium or high, explain what verification was done to mitigate the 
risks._
   
   ### Documentation Update
   
   _Describe any necessary documentation update if there is any new feature, 
config, or user-facing change. If not, put "none"._
   
   - _The config description must be updated if new configs are added or the 
default value of the configs are changed_
   - _Any new feature or user-facing change requires updating the Hudi website. 
Please create a Jira ticket, attach the
     ticket number here and follow the 
[instruction](https://hudi.apache.org/contribute/developer-setup#website) to 
make
     changes to the website._
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [ ] Change Logs and Impact were stated clearly
   - [ ] Adequate tests were added if applicable
   - [ ] CI passed
   


-- 
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