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.
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
[SPARK-50091][SQL] Handle case of aggregates in left-hand operand of IN-subquery #48627
[SPARK-50091][SQL] Handle case of aggregates in left-hand operand of IN-subquery #48627
Changes from all commits
79b5089
7fe2a08
c96af36
424d803
2b1a376
9c443b0
46d43fd
ca4dba8
e0fc82f
3e52a12
1db5316
f6aa964
cc6384b
93d98e7
cb4066a
b5ee466
0e1c170
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
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.
This rewrite only pulls out subquery expressions for
Aggregate#aggregateExpressions
, not grouping 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.
Re:
if exprsContainsAggregateInSubquery(resultExpressions) =>
.That won't work with
exprsContainsAggregateInSubquery
as it currently stands, since that function looks for in-subqueries with aggregate expressions in the left-hand operand.resultExpressions
has the aggregate expressions replaced with attributes, soexprsContainsAggregateInSubquery
would never trigger.Alternatively, I could do
which is kind of ugly, but does the trick.
Another alternative: I'm the only one calling
exprsContainsAggregateInSubquery
, so I could change it to return true if there are any in-subqueries at all with no regard to characteristics of the left-hand operand. We would end up rewriting some cases that wouldn't otherwise cause trouble.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.
ah OK, let's keep it as it is
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 also updated this test to check the whole optimized plan rather than simply testing that the join condition does not have an aggregate expression.