diff options
| author | Wenchen Fan <wenchen@databricks.com> | 2016-12-02 12:54:12 +0800 |
|---|---|---|
| committer | Wenchen Fan <wenchen@databricks.com> | 2016-12-02 12:54:12 +0800 |
| commit | a5f02b00291e0a22429a3dca81f12cf6d38fea0b (patch) | |
| tree | 2d2c4d35f53446f947469d2acf82a292ebf890da /conf | |
| parent | 38b9e69623c14a675b14639e8291f5d29d2a0bc3 (diff) | |
| download | spark-a5f02b00291e0a22429a3dca81f12cf6d38fea0b.tar.gz spark-a5f02b00291e0a22429a3dca81f12cf6d38fea0b.tar.bz2 spark-a5f02b00291e0a22429a3dca81f12cf6d38fea0b.zip | |
[SPARK-18647][SQL] do not put provider in table properties for Hive serde table
## What changes were proposed in this pull request?
In Spark 2.1, we make Hive serde tables case-preserving by putting the table metadata in table properties, like what we did for data source table. However, we should not put table provider, as it will break forward compatibility. e.g. if we create a Hive serde table with Spark 2.1, using `sql("create table test stored as parquet as select 1")`, we will fail to read it with Spark 2.0, as Spark 2.0 mistakenly treat it as data source table because there is a `provider` entry in table properties.
Logically Hive serde table's provider is always hive, we don't need to store it in table properties, this PR removes it.
## How was this patch tested?
manually test the forward compatibility issue.
Author: Wenchen Fan <wenchen@databricks.com>
Closes #16080 from cloud-fan/hive.
Diffstat (limited to 'conf')
0 files changed, 0 insertions, 0 deletions