aboutsummaryrefslogtreecommitdiff
path: root/bin/compute-classpath.sh
diff options
context:
space:
mode:
authorYash Datta <Yash.Datta@guavus.com>2015-03-26 21:13:38 +0800
committerCheng Lian <lian@databricks.com>2015-03-26 21:14:15 +0800
commit836c9216599b676ae8f421384f4f20fd35e8c53b (patch)
tree77b320bd059e9f918f8065d5dcd3f36ef935dd7b /bin/compute-classpath.sh
parent8254996557512b8bbc8fd35c550004b56144581f (diff)
downloadspark-836c9216599b676ae8f421384f4f20fd35e8c53b.tar.gz
spark-836c9216599b676ae8f421384f4f20fd35e8c53b.tar.bz2
spark-836c9216599b676ae8f421384f4f20fd35e8c53b.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 (cherry picked from commit 1c05027a143d1b0bf3df192984e6cac752b1e926) Signed-off-by: Cheng Lian <lian@databricks.com>
Diffstat (limited to 'bin/compute-classpath.sh')
0 files changed, 0 insertions, 0 deletions