Use exact distinct_count from statistics if exists for COUNT(DISTINCT column)) calculations#20845
Open
buraksenn wants to merge 4 commits intoapache:mainfrom
Open
Conversation
buraksenn
commented
Mar 10, 2026
| // expressions like casts or literals are not supported. | ||
| let col_expr = expr.as_any().downcast_ref::<expressions::Column>()?; | ||
| if let Precision::Exact(dc) = col_stats[col_expr.index()].distinct_count { | ||
| return Some(ScalarValue::Int64(Some(dc as i64))); |
Contributor
Author
There was a problem hiding this comment.
This assumes NULL is not counted in distinct_count column. AFAIS from the repository it is not counted so this should be ok but wanted to put a comment here
jonathanc-n
reviewed
Mar 10, 2026
Contributor
jonathanc-n
left a comment
There was a problem hiding this comment.
Thanks @buraksenn couple comments
| Ok(()) | ||
| } | ||
|
|
||
| fn mock_data_with_distinct_count( |
Contributor
There was a problem hiding this comment.
Are we able to combine these two functions
Contributor
Author
There was a problem hiding this comment.
I did not exactly understand but changed it to one table driven test
| // expressions like casts or literals are not supported. | ||
| let col_expr = expr.as_any().downcast_ref::<expressions::Column>()?; | ||
| if let Precision::Exact(dc) = col_stats[col_expr.index()].distinct_count { | ||
| return Some(ScalarValue::Int64(Some(dc as i64))); |
Contributor
There was a problem hiding this comment.
Distinct count is usize, we should deal with the case where it could overflow
Contributor
Author
There was a problem hiding this comment.
Since other paths were casting as well I did not do it actually but let me do it for all paths
xudong963
approved these changes
Mar 11, 2026
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.
Which issue does this PR close?
Does not close but part of #20766
Rationale for this change
If
distinct_countis known for the column from statistics we can directly use it inCOUNT(DISTINCT column))expressions instead of calculating.What changes are included in this PR?
Are these changes tested?
Added additional tests
Are there any user-facing changes?
No