diff options
| author | Wenchen Fan <wenchen@databricks.com> | 2016-09-01 16:45:22 +0800 |
|---|---|---|
| committer | Wenchen Fan <wenchen@databricks.com> | 2016-09-01 16:45:22 +0800 |
| commit | 8e740ae44d55570a3e7b6eae1f0239ac1319b986 (patch) | |
| tree | a4055f80643f9411cfb14d7ab51179ac0b83e047 /yarn | |
| parent | 1f06a5b6a0584d0c9656f58eaf54e54e2383c82b (diff) | |
| download | spark-8e740ae44d55570a3e7b6eae1f0239ac1319b986.tar.gz spark-8e740ae44d55570a3e7b6eae1f0239ac1319b986.tar.bz2 spark-8e740ae44d55570a3e7b6eae1f0239ac1319b986.zip | |
[SPARK-17257][SQL] the physical plan of CREATE TABLE or CTAS should take CatalogTable
## What changes were proposed in this pull request?
This is kind of a follow-up of https://github.com/apache/spark/pull/14482 . As we put `CatalogTable` in the logical plan directly, it makes sense to let physical plans take `CatalogTable` directly, instead of extracting some fields of `CatalogTable` in planner and then construct a new `CatalogTable` in physical plan.
## How was this patch tested?
existing tests.
Author: Wenchen Fan <wenchen@databricks.com>
Closes #14823 from cloud-fan/create-table.
Diffstat (limited to 'yarn')
0 files changed, 0 insertions, 0 deletions