-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-20688][SQL] correctly check analysis for scalar sub-queries #17930
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
Closed
Conversation
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
Contributor
Author
|
cc @rxin @gatorsmile |
|
Test build #76725 has started for PR 17930 at commit |
Member
|
LGTM |
Member
|
retest this please |
Contributor
|
Not introduced by this pr, but I just saw a if-else style nit here |
|
Test build #76733 has finished for PR 17930 at commit
|
|
Test build #76739 has finished for PR 17930 at commit
|
asfgit
pushed a commit
that referenced
this pull request
May 10, 2017
## What changes were proposed in this pull request? In `CheckAnalysis`, we should call `checkAnalysis` for `ScalarSubquery` at the beginning, as later we will call `plan.output` which is invalid if `plan` is not resolved. ## How was this patch tested? new regression test Author: Wenchen Fan <[email protected]> Closes #17930 from cloud-fan/tmp. (cherry picked from commit 789bdbe) Signed-off-by: Wenchen Fan <[email protected]>
asfgit
pushed a commit
that referenced
this pull request
May 10, 2017
In `CheckAnalysis`, we should call `checkAnalysis` for `ScalarSubquery` at the beginning, as later we will call `plan.output` which is invalid if `plan` is not resolved. new regression test Author: Wenchen Fan <[email protected]> Closes #17930 from cloud-fan/tmp. (cherry picked from commit 789bdbe) Signed-off-by: Wenchen Fan <[email protected]>
Contributor
Author
|
thanks for the review, merging to master/2.2/2.1! |
lycplus
pushed a commit
to lycplus/spark
that referenced
this pull request
May 24, 2017
## What changes were proposed in this pull request? In `CheckAnalysis`, we should call `checkAnalysis` for `ScalarSubquery` at the beginning, as later we will call `plan.output` which is invalid if `plan` is not resolved. ## How was this patch tested? new regression test Author: Wenchen Fan <[email protected]> Closes apache#17930 from cloud-fan/tmp.
jzhuge
pushed a commit
to jzhuge/spark
that referenced
this pull request
Aug 20, 2018
In `CheckAnalysis`, we should call `checkAnalysis` for `ScalarSubquery` at the beginning, as later we will call `plan.output` which is invalid if `plan` is not resolved. new regression test Author: Wenchen Fan <[email protected]> Closes apache#17930 from cloud-fan/tmp. (cherry picked from commit 789bdbe) Signed-off-by: Wenchen Fan <[email protected]>
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.
What changes were proposed in this pull request?
In
CheckAnalysis, we should callcheckAnalysisforScalarSubqueryat the beginning, as later we will callplan.outputwhich is invalid ifplanis not resolved.How was this patch tested?
new regression test