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


   ## What is the purpose of the pull request
   
   Adding virtual keys support for Metadata table
   
   ## Brief change log
   
   - Metadata table today has virtual keys disabled, thereby populating the 
metafields
     for each record written out and increasing the overall storage space used. 
Hereby
     adding virtual keys support for metadata table so that metafields are 
disabled
     for metadata table records.
   
   - HFile data blocks written out and read back assume the record key and 
partition
     path metafields are always available. After turning on the virtual keys, 
since
     these metafields are not available, added support for HFile/Avro data block
     readers, scanners to look at the table set record key property instead of 
the
     hardcoded metafield record key.
   
   
   ## 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