cshuo opened a new pull request, #18919: URL: https://github.com/apache/hudi/pull/18919
### Describe the issue this Pull Request addresses `hoodie.metadata.bloom.filter.enable` was not fully propagated through the metadata table read path. As a result, metadata file-group readers and HFile readers could be constructed without enabling the native HFile bloom filter lookup optimization, even when the metadata bloom filter config was set. This PR wires the existing metadata bloom filter config through the file-group reader properties and HFile reader factory so metadata table lookups, including record index reads, can correctly enable bloom-filter-backed full-key lookup. ### Summary and Changelog - Added `HoodieMetadataConfig.BLOOM_FILTER_ENABLE` to `ConfigUtils.buildFileGroupReaderProperties` so metadata reader configs carry the bloom filter setting into file-group readers. - Updated `HoodieAvroFileReaderFactory` to pass the bloom filter setting into `HoodieNativeAvroHFileReader` for path, `StoragePathInfo`, and in-memory content reader creation paths. - Added tests in `TestConfigUtils` and `TestHoodieAvroFileReaderFactory` covering config propagation, explicit true/false values, default behavior, and all HFile reader creation paths. ### Impact Existing `hoodie.metadata.bloom.filter.enable=true` settings now correctly enable native HFile bloom filter usage for metadata HFile full-key lookup paths. ### Risk Level low. The change is scoped to metadata reader config propagation and HFile reader construction, with tests covering the new config path and default disabled behavior. ### Documentation Update none. This fixes propagation for an existing config and does not introduce a new user-facing option. ### Contributor's checklist - [ ] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [ ] Enough context is provided in the sections above - [ ] 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]
