Skip to content

Conversation

@adrian-wang
Copy link
Contributor

Type coercion for IF should have children resolved first, or we could meet unresolved exception.

Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: Add a single line like "case e if !e.childrenResolved => e" will be enough?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure, it's equivalent.

@SparkQA
Copy link

SparkQA commented Aug 20, 2015

Test build #41307 has finished for PR 8331 at commit 1921f34.

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

@SparkQA
Copy link

SparkQA commented Aug 21, 2015

Test build #41348 has finished for PR 8331 at commit e206797.

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

@adrian-wang
Copy link
Contributor Author

@marmbrus

@jameszhouyi
Copy link

This is blocker issue and hopefully it is fixed in Spark 1.5.0, Thanks !

@marmbrus
Copy link
Contributor

Thanks, merging to master and 1.5

asfgit pushed a commit that referenced this pull request Aug 21, 2015
…d first

Type coercion for IF should have children resolved first, or we could meet unresolved exception.

Author: Daoyuan Wang <[email protected]>

Closes #8331 from adrian-wang/spark10130.

(cherry picked from commit 3c462f5)
Signed-off-by: Michael Armbrust <[email protected]>
@asfgit asfgit closed this in 3c462f5 Aug 21, 2015
@adrian-wang adrian-wang deleted the spark10130 branch August 24, 2015 08:39
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.

5 participants