manojpec opened a new pull request #3843:
URL: https://github.com/apache/hudi/pull/3843


   ## What is the purpose of the pull request
   
     When HoodieBackedTableMetadataWriter is instantiated for a writer client, 
it checks if
     bootstrapping is needed for the table for any un-synced instants. When the 
writer initiates
     a rollback action after the first commit (the one and only commit so far), 
the metadata table
     writer instantiation assumes bootstrapping is needed for the table as it 
fails to find its latest
     committed instant missing in the data table. And, while performing the 
bootstrapping it finds
     a pending action in the data table timeline and so fails the operation and 
the errors bubbles
     back to the writer client for the rollback action. The pending action for 
the data table is infact
     the rollback action which the writer is attempting to do. 
   
   ## Brief change log
   
     Fix is to make Metadata table writer creation aware of the currently 
inflight action so that it can
     make some informed decision about whether bootstrapping is needed for the 
table and whether
     any pending action on the data timeline can be ignored.
   
   ## Verify this pull request
   
     TestHBaseIndex::testEnsureTagLocationUsesCommitTimeline and 
::testSimpleTagLocationAndUpdateWithRollback
     is updated to include metadata table.
   
     New test case TestHoodieBackedMetadata::testFirstCommitRollback has been 
added to verify the fix
   
   ## Committer checklist
   
    - [ ] Has a corresponding JIRA in PR title & commit
    
    - [ ] Commit message is descriptive of the change
    
    - [ ] CI is green
   
    - [ ] Necessary doc changes done or have another open PR
          
    - [ ] For large changes, please consider breaking it into sub-tasks under 
an umbrella JIRA.
   


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