Parquet: Fix variant STRING metrics bounds to use UTF-8 byte order - #17397
Open
vishnuprakaz wants to merge 1 commit into
Open
Parquet: Fix variant STRING metrics bounds to use UTF-8 byte order#17397vishnuprakaz wants to merge 1 commit into
vishnuprakaz wants to merge 1 commit into
Conversation
uros-b
approved these changes
Jul 28, 2026
Member
|
Nice fix, thank you @vishnuprakaz! |
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
2 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.
Shredded variant
STRINGmetrics bounds are aggregated across row groups withString.compareTo(UTF-16 order), but Parquet stats and the scan-time evaluator (Comparators.charSequences()) use UTF-8 byte order. They disagree for supplementary-plane characters (code point >= U+10000):String.compareToorders them below BMP characters in U+E000..U+FFFF, while UTF-8 orders them above. When a string column spans row groups mixing the two, the aggregated bounds invert and the evaluator can skip files that contain matching rows. TheBINARYbranch already usesComparators.unsignedBytes()and the non-variant path usesComparators.charSequences(); only variantSTRINGfell through tonaturalOrder(). Same class of bug as #16880.the bug is present in 1.10.0 & 1.11.0 and backports will follow.