aajisaka opened a new pull request, #9567:
URL: https://github.com/apache/hudi/pull/9567

   This reverts commit 2567ada6d5654bf8463cb55e25f5d662aa5a8475 to solve #6940
   
    Conflicts:
        
hudi-hadoop-mr/src/main/java/org/apache/hudi/hadoop/HoodieCopyOnWriteTableInputFormat.java
        
hudi-hadoop-mr/src/main/java/org/apache/hudi/hadoop/realtime/HoodieMergeOnReadTableInputFormat.java
   
   ### Change Logs
   
   This commit is to add back the feature introduced in HUDI-5409, but changing 
the default value in the following snippet to true (=`ENABLE.defaultValue()`)
   
   ```
   if (conf.getBoolean(ENABLE.key(), ENABLE.defaultValue()) && 
HoodieTableMetadataUtil.isFilesPartitionAvailable(tableMetaClient)) {
   ```
   instead of false (=`DEFAULT_METADATA_ENABLE_FOR_READERS`) in 
https://github.com/apache/hudi/commit/cc1c1e7b33d9c95e5a2ba0e9a1db428d1e1b2a00#diff-b5d22feda93e8704a70c470565b00af58729230c6a30b411a848b9605d0f4090R252
   ```
   if (conf.getBoolean(ENABLE.key(), DEFAULT_METADATA_ENABLE_FOR_READERS) && 
HoodieTableMetadataUtil.isFilesPartitionAvailable(tableMetaClient)) {
   ```
   to avoid the performance issue observed in HUDI-5411 
(https://github.com/apache/hudi/pull/7526). In this way, users can set 
`hoodie.metadata.enabled` to `false` to get the same performance as Hudi 0.10.1 
when reading non-metadata partitioned tables.
   
   ### Impact
   
   No public API change. No performance impact in default configuration.
   
   ### Risk level (write none, low medium or high below)
   
   medium
   
   ### Documentation Update
   
   Not required.
   
   ### Contributor's checklist
   
   - [x] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Change Logs and Impact were stated clearly
   - [x] Adequate tests were added if applicable
   - [ ] CI passed
   


-- 
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