Skip to content

Conversation

@cloud-fan
Copy link
Contributor

The check was unreachable before, as case operator: LogicalPlan catches everything already.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think we do want to throw an error message here. We handle all case correctly today, but if we add new operator it could break and the result of planning a query with conflicting attributes is usually very confusing.

@cloud-fan cloud-fan changed the title [SPARK-9113][SQL] remove unnecessary analysis check code for self join [SPARK-9113][SQL] enable analysis check code for self join Jul 17, 2015
@SparkQA
Copy link

SparkQA commented Jul 17, 2015

Test build #37571 has finished for PR 7449 at commit 5493aea.

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

@SparkQA
Copy link

SparkQA commented Jul 17, 2015

Test build #37575 has finished for PR 7449 at commit 07385df.

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

@SparkQA
Copy link

SparkQA commented Jul 17, 2015

Test build #37586 has finished for PR 7449 at commit 2bb6637.

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

@marmbrus
Copy link
Contributor

Thanks for fixing this! Merging to master.

@asfgit asfgit closed this in fd6b310 Jul 17, 2015
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