Skip to content

docs: date the float value and null count divergence to Iceberg 1.9 #6681

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.

Sign up for GitHub

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
andygrove merged 1 commit into from
Oct 5, 2026
Merged

docs: date the float value and null count divergence to Iceberg 1.9 #6681

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/source/user-guide/latest/iceberg-writes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -366,7 +366,7 @@ iceberg-java's _writer-tracked_ state would have recorded, and both are analyzed
iceberg-java's writer-tracked bounds preserve the exact sign it saw. The native path's
manifest bounds inherit the normalised values — a strictly conservative widening that cannot
change pruning decisions.
- On Iceberg 1.10+, manifest `value_counts` / `null_value_counts` for float/double columns
- On Iceberg 1.9+, manifest `value_counts` / `null_value_counts` for float/double columns
nested under a nullable struct count rows whose parent struct is null (they come from the
parquet footer), while iceberg-java's writer-tracked counts do not. Both counts inflate by
the same amount, so the derived null ratios and `IS NULL` / `IS NOT NULL` pruning decisions
Expand Down