[fix](regression) check partition minmax only#65180
Merged
hello-stephen merged 1 commit intoJul 3, 2026
Merged
Conversation
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Collaborator
Author
|
run buildall |
englefly
approved these changes
Jul 3, 2026
Contributor
|
PR approved by at least one committer and no changes requested. |
github-actions
Bot
added
approved
Contributor
|
PR approved by anyone and no changes requested. |
yiguolei
pushed a commit
that referenced
this pull request
Jul 7, 2026
## Proposed changes Backport #65180 to branch-4.1. On branch-4.1, `partition_key_minmax` still lives under `nereids_p0/stats`, so this applies the same final fix to the branch-specific path instead of directly picking the master file path. The case is intended to validate partition-pruned partition-key min/max. The previous checks also depended on `ndv/count`, which can vary with async physical row-count reporting. This patch keeps the existing RANGE/LIST queries and checks only the partition-key min/max invariants. ## Testing - `git diff --check -- regression-test/suites/nereids_p0/stats/partition_key_minmax.groovy` - `git diff --check HEAD^ HEAD -- regression-test/suites/nereids_p0/stats/partition_key_minmax.groovy` Targeted regression was not run locally; CI will cover it.
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
4 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.
Proposed changes
partition_key_minmaxis intended to validate that partition-pruned memo-plan statistics tighten partition-key min/max for RANGE and LIST partitions.The previous exact checks also depended on
ndv/count, which are derived from selected partition row count and can vary with async physical row-count reporting (0,-1unknown, or positive). Waiting for physical row count viashow index statswas too strict and caused P0 timeout when strict row count stayed-1.This patch removes the physical row-count wait and uses
check {}to assert only the partition-key min/max invariants:a#0hasmin=5and an accepted max of30or22id#0hasmin=max=3Testing
git diff --checkTargeted regression was not run locally; CI will cover it.