usberkeley commented on PR #12244: URL: https://github.com/apache/hudi/pull/12244#issuecomment-2472917036
### Infor Summary #### 1. In #11028, we already fixed the unnecessary rewrite when the schemas are exactly the same, is your benchmark based on the fix then? Yes #### 2. Why are `allowOperationMetadataField` allowed only when `populateMetaFields` is enabled? 1) Disabling `populateMetaFields` can reduce the performance overhead of decoding HoodieRecords. However, if `allowOperationMetadataField` is enabled, decoding performance is still affected even if `populateMetaFields` is disabled. Therefore, the impact of these two settings on performance is interconnected. 2) Both are metadata fields. `populateMetaFields` is the main switch, while `allowOperationMetadataField` just controls the activation of specific metadata fields. When the main switch is off, the sub-switches should have no effect. #### 3. When enable `populateMetaFields`, why the number of record key fields must be equal to one？ The Log Scanner needs to regenerate the Record Key. Currently, it only supports a simple key generator, which means there can only be one primary key column. -- 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]
