Skip to content

Conversation

@gatorsmile
Copy link
Member

What changes were proposed in this pull request?

This PR is to clean the related codes majorly based on the today's code review on #19559

How was this patch tested?

N/A

@gatorsmile
Copy link
Member Author

cc @cloud-fan @jiangxb1987

Copy link
Contributor

@jiangxb1987 jiangxb1987 left a comment

Choose a reason for hiding this comment

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

LGTM pending jenkins

@SparkQA
Copy link

SparkQA commented Oct 27, 2017

Test build #83109 has finished for PR 19585 at commit b23dd7b.

  • This patch fails due to an unknown error code, -9.
  • This patch merges cleanly.
  • This patch adds no public classes.

@gatorsmile
Copy link
Member Author

retest this please

@SparkQA
Copy link

SparkQA commented Oct 27, 2017

Test build #83115 has finished for PR 19585 at commit b23dd7b.

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

@gatorsmile
Copy link
Member Author

Thanks! Merged to master.

@asfgit asfgit closed this in 36b826f Oct 27, 2017

case q: LogicalPlan =>
logTrace(s"Attempting to resolve ${q.simpleString}")
q.transformExpressionsUp {
Copy link
Contributor

Choose a reason for hiding this comment

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

can you provide more context here? The previous code resolve reference bottom-up, so that we can resolve a.b.c.d with one round. The new code changes to top-down, why?

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