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

   ### Describe the issue this Pull Request addresses
   
   The Spark 4.1 PR (#17674) was open from December 2025 to April 2026. During 
that window, #17661 replaced direct `HoodieHadoopStorage` instantiation with 
`HoodieStorageUtils.getStorage(...)` across 
`hudi-spark3.3.x`/`3.4.x`/`3.5.x`/`4.0.x`, but the in-flight Spark 4.1 branch 
was not rebased to pick it up.
   
   As a result, `Spark41LegacyHoodieParquetFileFormat` is the only legacy 
parquet read path left that bypasses the `hoodie.storage.class` config plumbing 
— any user-configured custom `HoodieStorage` implementation is silently ignored 
on Spark 4.1.
   
   ### Summary and Changelog
   
   Mirror the one-line change from #17661 in 
`Spark41LegacyHoodieParquetFileFormat.scala`:
   
   - Import `HoodieStorageUtils` and `HadoopFSUtils` instead of 
`HoodieHadoopStorage`.
   - Replace `new HoodieHadoopStorage(tablePath, sharedConf)` with 
`HoodieStorageUtils.getStorage(tablePath, 
HadoopFSUtils.getStorageConf(sharedConf))`.
   
   No behavior change for the default `HoodieHadoopStorage`; the difference is 
only visible when `hoodie.storage.class` is overridden.
   
   ### Impact
   
   - Custom `HoodieStorage` implementations now take effect on the Spark 4.1 
legacy parquet read path, matching the behavior of all other Spark version 
modules.
   - No public API or config change.
   
   ### Risk Level
   
   low — three-line cherry-pick of an established refactor pattern that has 
been in production on every other Spark version module since #17661 merged.
   
   ### Documentation Update
   
   none
   
   ### Contributor's checklist
   
   - [x] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Enough context is provided in the sections above
   - [x] Adequate tests were added if applicable


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