-
Notifications
You must be signed in to change notification settings - Fork 166
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: Aggregation without aggregation expressions should use correct result expressions #175
Conversation
val attributes = groupingExpressions.map(_.toAttribute) ++ aggregateAttributes | ||
val resultExprs = resultExpressions.map(exprToProto(_, attributes)) | ||
if (resultExprs.exists(_.isEmpty)) { | ||
emitWarning(s"Unsupported result expressions found in: ${resultExpressions}") | ||
return None | ||
} |
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.
Even aggregateExpressions
is empty, we still need to assign result expressions. This is the latest bug I found during fixing TPCDS query failures in SortMergeJoin work.
…esult expressions
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 (pending CI)
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #175 +/- ##
=========================================
Coverage 33.29% 33.29%
Complexity 766 766
=========================================
Files 107 107
Lines 35379 35385 +6
Branches 7657 7658 +1
=========================================
+ Hits 11778 11781 +3
- Misses 21155 21157 +2
- Partials 2446 2447 +1 ☔ View full report in Codecov by Sentry. |
Merged. Thanks. |
Which issue does this PR close?
Closes #176.
Rationale for this change
What changes are included in this PR?
How are these changes tested?