Skip to content

Conversation

@nongli
Copy link
Contributor

@nongli nongli commented Dec 11, 2015

No description provided.

@nongli nongli changed the title [SPARK-12271][SQL] Improve error message when Dataset.as has incompatible schemas. [SPARK-12271][SQL] Improve error message when Dataset.as[ ] has incompatible schemas. Dec 11, 2015
@SparkQA
Copy link

SparkQA commented Dec 11, 2015

Test build #47560 has finished for PR 10260 at commit ceed59b.

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

Copy link
Contributor

Choose a reason for hiding this comment

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

the simpleString of attribute includes expr id, which I think is noisy to users, should we generate the string manually or use StructType.fromAttributes to turn schema into StructType and call StrcutType.simpleString?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

@holdenk
Copy link
Contributor

holdenk commented Dec 14, 2015

Could you maybe update the PR description to include the description from the JIRA?

@SparkQA
Copy link

SparkQA commented Dec 14, 2015

Test build #47680 has finished for PR 10260 at commit f177d55.

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

asfgit pushed a commit that referenced this pull request Dec 15, 2015
I think it was a mistake, and we have not catched it so far until #10260 which begin to check if the `fromRowExpression` is resolved.

Author: Wenchen Fan <[email protected]>

Closes #10263 from cloud-fan/encoder.
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a reason to not just put this in CheckAnalysis and make it more general (i.e. not just Project)? I realize its only used here now, but if we ever do use it elsewhere, its invalid to remain after analysis.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

much better!

@marmbrus
Copy link
Contributor

This looks great now!

LGTM pending tests / conflict resolution

@SparkQA
Copy link

SparkQA commented Dec 15, 2015

Test build #47747 has finished for PR 10260 at commit 359b3e2.

  • This patch passes all tests.
  • This patch does not merge cleanly.
  • This patch adds the following public classes (experimental):\n * case class WrapOption(child: Expression, optType: DataType)\n

@SparkQA
Copy link

SparkQA commented Dec 15, 2015

Test build #47754 has finished for PR 10260 at commit b5007d7.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds the following public classes (experimental):\n * case class WrapOption(child: Expression, optType: DataType)\n

@cloud-fan
Copy link
Contributor

LGTM

@marmbrus
Copy link
Contributor

Thanks, merging to master.

@asfgit asfgit closed this in 86ea64d Dec 16, 2015
@nongli nongli deleted the spark-11271 branch December 16, 2015 05:04
marmbrus pushed a commit to marmbrus/spark that referenced this pull request Jan 7, 2016
I think it was a mistake, and we have not catched it so far until apache#10260 which begin to check if the `fromRowExpression` is resolved.

Author: Wenchen Fan <[email protected]>

Closes apache#10263 from cloud-fan/encoder.
marmbrus pushed a commit to marmbrus/spark that referenced this pull request Jan 7, 2016
…patible schemas.

Author: Nong Li <[email protected]>

Closes apache#10260 from nongli/spark-11271.
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