Repository navigation
GH-3826: [1.18.x] Preserve component paths for Bloom filters - #3873
Merged
wgtmac merged 1 commit intoOct 21, 2026
Merged
Conversation
Backport apache#3827. Preserve component boundaries in Bloom-filter maps and rewriter calls; retain the legacy API with ambiguity checks. (cherry picked from commit 6ae2a8f) Co-authored-by: Codex <codex@openai.com>
wgtmac
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale for this change
Backport #3827 to
parquet-1.18.xto prevent colliding column paths from receiving the wrong Bloom filter.What changes are included in this PR?
Cherry-picks
6ae2a8f1, including component-based Bloom-filter maps, the structured-path API, rewriter handling, and regression tests.Are these changes tested?
Passed: Java 17 / Thrift 0.23.0 focused reactor verification for
TestParquetFileWriter,TestParquetWriter, andParquetRewriterTest(162 tests, 0 skipped); Spotless andgit diff --check. Broad integration tests and Javadocs were skipped.Are there any user-facing changes?
The legacy string API rejects ambiguous paths; structured callers preserve component boundaries. Newly written filters are corrected; existing files are not repaired.