Skip to content
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-15915][SQL] Logical plans should use subqueries eliminated plan when override sameResult. #13668

Closed
wants to merge 2 commits into from

Conversation

ueshin
Copy link
Member

@ueshin ueshin commented Jun 14, 2016

What changes were proposed in this pull request?

This pr is a backport of #13638 for branch-1.6.

How was this patch tested?

Added the same test as #13638 modified for branch-1.6.

@cloud-fan
Copy link
Contributor

LGTM

@SparkQA
Copy link

SparkQA commented Jun 14, 2016

Test build #60503 has finished for PR 13668 at commit e51774f.

  • This patch fails to build.
  • This patch merges cleanly.
  • This patch adds no public classes.

@ueshin
Copy link
Member Author

ueshin commented Jun 14, 2016

Jenkins, retest this please.

@SparkQA
Copy link

SparkQA commented Jun 14, 2016

Test build #60505 has finished for PR 13668 at commit e51774f.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@ueshin
Copy link
Member Author

ueshin commented Jun 15, 2016

Jenkins, retest this please.

@SparkQA
Copy link

SparkQA commented Jun 15, 2016

Test build #60539 has finished for PR 13668 at commit e51774f.

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

otherOutput.map(_.dataType) == output.map(_.dataType) && otherData == data
case _ => false
override def sameResult(plan: LogicalPlan): Boolean = {
EliminateSubQueries(plan) match {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should execute EliminateSubQueries when looking up cache entry? 1.6 is not like 2.0, we don't have the canonized method and can't memorize the result of EliminateSubQueries.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm sorry but I couldn't find the reason.
Is the purpose to execute EliminateSubQueries to memorize the result of it?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nvm, I was wrong

asfgit pushed a commit that referenced this pull request Jun 15, 2016
…n when override sameResult.

## What changes were proposed in this pull request?

This pr is a backport of #13638 for `branch-1.6`.

## How was this patch tested?

Added the same test as #13638 modified for `branch-1.6`.

Author: Takuya UESHIN <[email protected]>

Closes #13668 from ueshin/issues/SPARK-15915_1.6.
@cloud-fan
Copy link
Contributor

thanks, merging to 1.6!

@ueshin can you close this PR? it won't be closed automatically.

@ueshin
Copy link
Member Author

ueshin commented Jun 15, 2016

@cloud-fan Sure, thank you for merging this!

@ueshin ueshin closed this Jun 15, 2016
zzcclp pushed a commit to zzcclp/spark that referenced this pull request Jun 16, 2016
…n when override sameResult.

## What changes were proposed in this pull request?

This pr is a backport of apache#13638 for `branch-1.6`.

## How was this patch tested?

Added the same test as apache#13638 modified for `branch-1.6`.

Author: Takuya UESHIN <[email protected]>

Closes apache#13668 from ueshin/issues/SPARK-15915_1.6.

(cherry picked from commit cffc080)
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.

3 participants