Fix min/max value in Iceberg writes#91589
Merged
scanhex12 merged 1 commit intoClickHouse:25.8from Jan 29, 2026
Merged
Conversation
Contributor
|
Workflow [BackportPR], commit [f70f7a9] |
scanhex12
approved these changes
Dec 24, 2025
25 tasks
Contributor
Author
|
Failed test |
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.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
Fix min/max value in Iceberg writes
Documentation entry for user-facing changes
Only in 25.8 LTS.
During writing in Iceberg table ClickHouse incorrectly counts minimal and maximal values for columns.
As result min/max pruning works incorrectly.
In 25.9 code was refactored, in new variant min/max counted correctly.