-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Validate FIXED_LEN_BYTE_ARRAY length for DECIMAL and INTERVAL types #9985
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
etseidl
merged 5 commits into
apache:main
from
CynicDog:validate-type-length-decimal-interval
May 28, 2026
+131
−1
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
ee432be
Validate FIXED_LEN_BYTE_ARRAY length for DECIMAL and INTERVAL types
CynicDog 9b2a4f3
address review comments on check_decimal_length
CynicDog af944ea
suppress clippy::manual_range_contains to preserve explicit bounds check
CynicDog 8bc991a
Merge branch 'main' into validate-type-length-decimal-interval
CynicDog 016970b
Merge branch 'main' into validate-type-length-decimal-interval
CynicDog File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be checking exact lengths? The only valid lengths in this case are 16 and 32 , right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch on the wording! You're totally right—any byte length is valid here, not just 16 or 32.
As per the Parquet spec for
fixed_len_byte_array, the precision is simply limited by the array size. As long as the precision fits within the byte length, it's completely valid.That upper bound of 32 we were looking at is actually an Arrow constraint (since
Decimal256is 256 bits, which caps it at 32 bytes), rather than a limitation from Parquet itself. Checking for a range of1..=32makes perfect sense here, especially since we definitely see perfectly legitimate Parquet files out in the wild with byte lengths like 4 or 7.