diff options
author | Yin Huai <yhuai@databricks.com> | 2015-08-20 15:30:31 +0800 |
---|---|---|
committer | Cheng Lian <lian@databricks.com> | 2015-08-20 15:30:31 +0800 |
commit | 43e0135421b2262cbb0e06aae53523f663b4f959 (patch) | |
tree | fd2968f64192cb676e03a46fb6f5c4a2342a18e3 /python/pyspark/sql/types.py | |
parent | b762f9920f7587d3c08493c49dd2fede62110b88 (diff) | |
download | spark-43e0135421b2262cbb0e06aae53523f663b4f959.tar.gz spark-43e0135421b2262cbb0e06aae53523f663b4f959.tar.bz2 spark-43e0135421b2262cbb0e06aae53523f663b4f959.zip |
[SPARK-10092] [SQL] Multi-DB support follow up.
https://issues.apache.org/jira/browse/SPARK-10092
This pr is a follow-up one for Multi-DB support. It has the following changes:
* `HiveContext.refreshTable` now accepts `dbName.tableName`.
* `HiveContext.analyze` now accepts `dbName.tableName`.
* `CreateTableUsing`, `CreateTableUsingAsSelect`, `CreateTempTableUsing`, `CreateTempTableUsingAsSelect`, `CreateMetastoreDataSource`, and `CreateMetastoreDataSourceAsSelect` all take `TableIdentifier` instead of the string representation of table name.
* When you call `saveAsTable` with a specified database, the data will be saved to the correct location.
* Explicitly do not allow users to create a temporary with a specified database name (users cannot do it before).
* When we save table to metastore, we also check if db name and table name can be accepted by hive (using `MetaStoreUtils.validateName`).
Author: Yin Huai <yhuai@databricks.com>
Closes #8324 from yhuai/saveAsTableDB.
Diffstat (limited to 'python/pyspark/sql/types.py')
0 files changed, 0 insertions, 0 deletions