[iceberg] Omit unknown null counts and bounds in IcebergDataFileMeta#8732
Merged
JingsongLi merged 1 commit intoJul 20, 2026
Merged
Conversation
Contributor
|
+1 |
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
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.
Purpose
IcebergDataFileMeta.createpublishes wrong stats when aSimpleStatsslot isunknown (null), silently corrupting Iceberg's metrics-based pruning:
0, soIS NULLpruning skips filesthat actually contain nulls;
a non-nullable type has none) and published as garbage bounds like
[0, 0];reading the stats slots, which can crash on a required field.
Unknown counts and bounds are now omitted (a missing entry means unknown per the
Iceberg spec), the getter is built from the nullable copy of the type, and the
eligibility check runs before any slot is read. No format or API change.