-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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.
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
[fix](agg)disallow group by bitmap or hll data type #11782
Conversation
@@ -160,6 +161,15 @@ public void setPartitionExprs(List<Expr> exprs) { | |||
partitionExprs = exprs; | |||
} | |||
|
|||
private static void validateGroupingExprs(List<Expr> groupingExprs) throws AnalysisException { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is more reasonable to put this checking logic into GroupByClause
's analyze phase.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your time. But there is no group by clause in sql like "select distinct bitmap, hll from xxx", the agg node is created by fe to implement the "distinct" operator, so no analyze function is called in that case. Anyway, I update the error message which is consistent with the error "select count(*) from xxx group by bitmap" now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
* [fix](agg)disallow group by bitmap or hll data type
Proposed changes
disallow "select distinct bitmap, hll from xxx", because in some case, the FE will introduce a agg node with group by bitmap or hll exprs to implement the "distinct" operator. But group by bitmap or hll data type are not supported in BE.
Problem summary
Describe your changes.
Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...