rmpifer opened a new pull request #2902:
URL: https://github.com/apache/hudi/pull/2902


   ## *Tips*
   - *Thank you very much for contributing to Apache Hudi.*
   - *Please review https://hudi.apache.org/contributing.html before opening a 
pull request.*
   
   ## What is the purpose of the pull request
   
   Small file size handling right now considers file groups in pending 
compaction. However when a compaction is in progress, there are no base or log 
files present yet in the file group. Small file sizing code expects either a 
base or log file is present and will throw an exception
   
   JIRA: https://issues.apache.org/jira/browse/HUDI-1800
   GH Issue: https://github.com/apache/hudi/issues/2633
   
   ## Brief change log
   
   Excludes pending compactions from consideration when performing small file 
sizing. Based on conversation in GH decided to move forward with this approach
   
   *(for example:)*
     - *Modify AnnotationLocation checkstyle rule in checkstyle.xml*
   
   ## Verify this pull request
   
   Was able to reproduce error in the unit test added
   
   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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to