Skip to content

Conversation

@cloud-fan
Copy link
Contributor

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

@cloud-fan
Copy link
Contributor Author

cc @rxin @gatorsmile

@SparkQA
Copy link

SparkQA commented May 10, 2017

Test build #76725 has started for PR 17930 at commit 3ccff2e.

@gatorsmile
Copy link
Member

LGTM

@gatorsmile
Copy link
Member

retest this please

@wzhfy
Copy link
Contributor

wzhfy commented May 10, 2017

Not introduced by this pr, but I just saw a if-else style nit here

             if (conditions.isEmpty && query.output.size != 1) {
                failAnalysis(
                 s"Scalar subquery must return only one column, but got ${query.output.size}")
             }
             else if (conditions.nonEmpty) {

@SparkQA
Copy link

SparkQA commented May 10, 2017

Test build #76733 has finished for PR 17930 at commit 3ccff2e.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented May 10, 2017

Test build #76739 has finished for PR 17930 at commit 013137f.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

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 asfgit closed this in 789bdbe May 10, 2017
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]>
@cloud-fan
Copy link
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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants