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


   ## What is the purpose of the pull request
   
   When metadata table is created and when it decides to the initialization
   from the filesystem for the user dataset, all the enabled partitions need
   to be initialized along with FILES partition. This fix adds init support
   for bloom filter and column stats partitions.
   
   ## Brief change log
   
   Since the initialization can be for a huge set of files, the records prepared
   are in HoodieData<HoodieRecord> format so that they can be passed on
   to engine specific commit without materialization at the driver and avoid 
OOME.
   
   PS: This is stacked on top of https://github.com/apache/hudi/pull/4740
   Commit to review:  
https://github.com/apache/hudi/commit/9c4b90bbbed70350f5197b29f5477fada2d091b5
   
   *(for example:)*
     - *Modify AnnotationLocation checkstyle rule in checkstyle.xml*
   
   ## 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