diff options
| author | Yash Datta <Yash.Datta@guavus.com> | 2015-03-26 21:13:38 +0800 |
|---|---|---|
| committer | Cheng Lian <lian@databricks.com> | 2015-03-26 21:13:38 +0800 |
| commit | 1c05027a143d1b0bf3df192984e6cac752b1e926 (patch) | |
| tree | f9ac6606175278fa2ef3896613f1fcbf654c97a1 /core | |
| parent | 0c88ce5416d7687bc806a7655e17009ad5823d30 (diff) | |
| download | spark-1c05027a143d1b0bf3df192984e6cac752b1e926.tar.gz spark-1c05027a143d1b0bf3df192984e6cac752b1e926.tar.bz2 spark-1c05027a143d1b0bf3df192984e6cac752b1e926.zip | |
[SQL][SPARK-6471]: Metastore schema should only be a subset of parquet schema to support dropping of columns using replace columns
Currently in the parquet relation 2 implementation, error is thrown in case merged schema is not exactly the same as metastore schema.
But to support cases like deletion of column using replace column command, we can relax the restriction so that even if metastore schema is a subset of merged parquet schema, the query will work.
Author: Yash Datta <Yash.Datta@guavus.com>
Closes #5141 from saucam/replace_col and squashes the following commits:
e858d5b [Yash Datta] SPARK-6471: Fix test cases, add a new test case for metastore schema to be subset of parquet schema
5f2f467 [Yash Datta] SPARK-6471: Metastore schema should only be a subset of parquet schema to support dropping of columns using replace columns
Diffstat (limited to 'core')
0 files changed, 0 insertions, 0 deletions