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-20195][SPARKR][SQL] add createTable catalog API and deprecate createExternalTable #17511

Closed
wants to merge 3 commits into from

Conversation

felixcheung
Copy link
Member

What changes were proposed in this pull request?

Following up on #17483, add createTable (which is new in 2.2.0) and deprecate createExternalTable, plus a number of minor fixes

How was this patch tested?

manual, unit tests

@SparkQA
Copy link

SparkQA commented Apr 2, 2017

Test build #75465 has finished for PR 17511 at commit b424a52.

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

@SparkQA
Copy link

SparkQA commented Apr 2, 2017

Test build #75467 has finished for PR 17511 at commit cd84730.

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

@felixcheung
Copy link
Member Author

@gatorsmile @shivaram

@SparkQA
Copy link

SparkQA commented Apr 4, 2017

Test build #75512 has finished for PR 17511 at commit 6806513.

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

@@ -557,7 +557,7 @@ setMethod("insertInto",
jmode <- convertToJSaveMode(ifelse(overwrite, "overwrite", "append"))
write <- callJMethod(x@sdf, "write")
write <- callJMethod(write, "mode", jmode)
callJMethod(write, "insertInto", tableName)
invisible(callJMethod(write, "insertInto", tableName))
Copy link
Member

Choose a reason for hiding this comment

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

Just wondering what is the reason why we add invisible in this PR? Is it related to this deprecation?

Copy link
Member Author

@felixcheung felixcheung Apr 5, 2017

Choose a reason for hiding this comment

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

It's a R usability thing: for method not returning any value (in these cases the Scala method is defined as foo : Unit), it will print NULL.

so we say invisible to get it to not print out the value, that's all

so no, it's not really related to this deprecation - it's probably been around for quite a while

@felixcheung
Copy link
Member Author

merged to master

@asfgit asfgit closed this in 5a693b4 Apr 6, 2017
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