-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-29145][SQL][FOLLOWUP] Clean up code about support sub-queries in join conditions #32499
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
Conversation
|
FYI @cloud-fan |
| resolveSubQueries(q, q.children) | ||
| case j: Join if j.childrenResolved => | ||
| resolveSubQueries(j, Seq(j, j.left, j.right)) | ||
| resolveSubQueries(j, Seq(j.left, j.right)) |
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.
nit: j.children
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.
nit:
j.children
Done
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #138370 has finished for PR 32499 at commit
|
|
Test build #138368 has finished for PR 32499 at commit
|
| // Only a few unary nodes (Project/Filter/Aggregate) can contain subqueries. | ||
| case q: UnaryNode if q.childrenResolved => | ||
| resolveSubQueries(q, q.children) | ||
| case j: Join if j.childrenResolved => |
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.
seems we should also check j.duplicateResolved
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.
Done, but I am confused witch case will cause error.
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #138381 has finished for PR 32499 at commit
|
|
Is the title correct? It seems a clean-up fix. |
Hmmm how about current? |
|
thanks, merging to master! |
What changes were proposed in this pull request?
According to discuss #25854 (comment)
Why are the changes needed?
Clean code
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existed UT