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

   Summary:
   On metadata table deltacommmit timestamp is equivalent to main table 
commit's timestamp. So, if metadata sync fails it reuses the same timestamp. 
This change fixes the case where the log blocks are treated as valid if their 
corresponding rollback is already visited.
   
   Reviewers: balajee, O955 Project Hoodie Project Reviewer: Add blocking 
reviewers, PHID-PROJ-pxfpotkfgkanblb3detq!
   
   Reviewed By: balajee, O955 Project Hoodie Project Reviewer: Add blocking 
reviewers
   
   JIRA Issues: HUDI-1868
   
   Differential Revision: https://code.uberinternal.com/D8110297
   
   ### Change Logs
   
   _Describe context and summary for this change. Highlight if any code was 
copied._
   
   ### Impact
   
   _Describe any public API or user-facing feature change or any performance 
impact._
   
   ### 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_
   
   - _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