Uh oh!
There was an error while loading. Please reload this page.
[SPARK-19148][SQL] do not expose the external table concept in Catalog - #16528
[SPARK-19148][SQL] do not expose the external table concept in Catalog#16528cloud-fan wants to merge 3 commits into
Conversation
There was a problem hiding this comment.
minor code cleanup, not related to this PR.
There was a problem hiding this comment.
How about we revert this change?
There was a problem hiding this comment.
We will never hit this branch after this PR. There is no public API to set the table type and users can only set custom table path, so we will never create an external table without path
cloud-fan
commented
Jan 10, 2017
SparkQA
commented
Jan 10, 2017
Test build #71123 has finished for PR 16528 at commit
|
SparkQA
commented
Jan 10, 2017
Test build #71125 has finished for PR 16528 at commit
|
cloud-fan
commented
Jan 10, 2017
retest this please |
SparkQA
commented
Jan 10, 2017
Test build #71128 has finished for PR 16528 at commit
|
gatorsmile
commented
Jan 10, 2017
retest this please |
| /** | ||
| * :: Experimental :: | ||
| * Creates a table from the given path and returns the corresponding DataFrame. |
There was a problem hiding this comment.
Maybe we can explain here to say the data files will not be dropped when dropping the table?
There was a problem hiding this comment.
we already documented this in programming guide. If we wanna explain the custom path here, there are a lot of similar places we need to add comments too. So I'd like to leave it as it was.
gatorsmile
commented
Jan 10, 2017
If we compare the above two interfaces, the Catalog's |
gatorsmile
commented
Jan 10, 2017
We also need to update the Python interface. See the code |
SparkQA
commented
Jan 10, 2017
Test build #71143 has finished for PR 16528 at commit
|
cloud-fan
commented
Jan 11, 2017
I'd like to do it in follow-ups I'll update the python api too |
SparkQA
commented
Jan 11, 2017
Test build #71175 has finished for PR 16528 at commit
|
SparkQA
commented
Jan 11, 2017
Test build #71191 has started for PR 16528 at commit |
gatorsmile
commented
Jan 11, 2017
retest this please |
SparkQA
commented
Jan 11, 2017
Test build #71198 has finished for PR 16528 at commit
|
SparkQA
commented
Jan 11, 2017
Test build #71214 has finished for PR 16528 at commit
|
SparkQA
commented
Jan 12, 2017
Test build #71238 has finished for PR 16528 at commit
|
SparkQA
commented
Jan 13, 2017
Test build #71292 has finished for PR 16528 at commit
|
SparkQA
commented
Jan 13, 2017
Test build #71316 has finished for PR 16528 at commit
|
SparkQA
commented
Jan 13, 2017
Test build #71325 has finished for PR 16528 at commit
|
| warnings.warn( | ||
| "createExternalTable is deprecated since Spark 2.2, please use createTable instead.", | ||
| DeprecationWarning) | ||
| return self.createTable(tableName, path, source, schema, **options) |
There was a problem hiding this comment.
it's python syntax, like what we do in scala: func(options: _*)
There was a problem hiding this comment.
Yeah. Got it. I also manually tried it in pyspark. It works fine.
gatorsmile
commented
Jan 14, 2017
LGTM |
gatorsmile
commented
Jan 15, 2017
ok to test |
SparkQA
commented
Jan 16, 2017
Test build #71408 has finished for PR 16528 at commit
|
cloud-fan
commented
Jan 16, 2017
cc @yhuai for final sign-off |
looks good to me. If possible, I'd like to get the code mentioned by https://github.com/apache/spark/pull/16528/files#r96314156 reverted. |
SparkQA
commented
Jan 17, 2017
Test build #71469 has finished for PR 16528 at commit
|
cloud-fan
commented
Jan 17, 2017
thanks for the review, merging to master! |
## What changes were proposed in this pull request? In apache#16296 , we reached a consensus that we should hide the external/managed table concept to users and only expose custom table path. This PR renames `Catalog.createExternalTable` to `createTable`(still keep the old versions for backward compatibility), and only set the table type to EXTERNAL if `path` is specified in options. ## How was this patch tested? new tests in `CatalogSuite` Author: Wenchen Fan <wenchen@databricks.com> Closesapache#16528 from cloud-fan/create-table.
## What changes were proposed in this pull request? In apache#16296 , we reached a consensus that we should hide the external/managed table concept to users and only expose custom table path. This PR renames `Catalog.createExternalTable` to `createTable`(still keep the old versions for backward compatibility), and only set the table type to EXTERNAL if `path` is specified in options. ## How was this patch tested? new tests in `CatalogSuite` Author: Wenchen Fan <wenchen@databricks.com> Closesapache#16528 from cloud-fan/create-table.
…t in Catalog ### What changes were proposed in this pull request? After we renames `Catalog`.`createExternalTable` to `createTable` in the PR: apache#16528, we also need to deprecate the corresponding functions in `SQLContext`. ### How was this patch tested? N/A Author: Xiao Li <gatorsmile@gmail.com> Closesapache#17502 from gatorsmile/deprecateCreateExternalTable.
What changes were proposed in this pull request?
In #16296 , we reached a consensus that we should hide the external/managed table concept to users and only expose custom table path.
This PR renames
Catalog.createExternalTabletocreateTable(still keep the old versions for backward compatibility), and only set the table type to EXTERNAL ifpathis specified in options.How was this patch tested?
new tests in
CatalogSuite