zhangyue19921010 opened a new pull request #3545:
URL: https://github.com/apache/hudi/pull/3545


   https://issues.apache.org/jira/browse/HUDI-2355
   ## What is the purpose of the pull request
   
   After  https://github.com/apache/hudi/pull/3310 merged, replaced data file 
is cleaned in cleaner service. But if replacecommit file deleted by archival, 
cleaner service can not delete the replaced data file anymore.
   
   ## Brief change log
   Just change the execution order between cleaner and archival services.
   
              -> cleaner service starts first then archival service works.
   
   For sync clean, we trigger clean first. After clean finished then trigger 
archival service
   For async clean, we will wait cleaner service finished in `postCommit` 
function and then trigger archival service.
   
   This change is tested on dev env.
   
   ## Verify this pull request
   
   *(Please pick either of the following options)*
   
   This pull request is a trivial rework / code cleanup without any test 
coverage.
   
   *(or)*
   
   This pull request is already covered by existing tests, such as *(please 
describe tests)*.
   
   (or)
   
   This change added tests and can be verified as follows:
   
   *(example:)*
   
     - *Added integration tests for end-to-end.*
     - *Added HoodieClientWriteTest to verify the change.*
     - *Manually verified the change by running a job locally.*
   
   ## 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