aboutsummaryrefslogtreecommitdiff
path: root/sbin/start-master.sh
diff options
context:
space:
mode:
authorWenchen Fan <wenchen@databricks.com>2015-11-08 21:01:53 -0800
committerYin Huai <yhuai@databricks.com>2015-11-08 21:01:53 -0800
commitd8b50f70298dbf45e91074ee2d751fee7eecb119 (patch)
treead2b1418e3684630bd0ac18349e9c559bbf4782c /sbin/start-master.sh
parent97b7080cf2d2846c7257f8926f775f27d457fe7d (diff)
downloadspark-d8b50f70298dbf45e91074ee2d751fee7eecb119.tar.gz
spark-d8b50f70298dbf45e91074ee2d751fee7eecb119.tar.bz2
spark-d8b50f70298dbf45e91074ee2d751fee7eecb119.zip
[SPARK-11453][SQL] append data to partitioned table will messes up the result
The reason is that: 1. For partitioned hive table, we will move the partitioned columns after data columns. (e.g. `<a: Int, b: Int>` partition by `a` will become `<b: Int, a: Int>`) 2. When append data to table, we use position to figure out how to match input columns to table's columns. So when we append data to partitioned table, we will match wrong columns between input and table. A solution is reordering the input columns before match by position, like what we did for [`InsertIntoHadoopFsRelation`](https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/InsertIntoHadoopFsRelation.scala#L101-L105) Author: Wenchen Fan <wenchen@databricks.com> Closes #9408 from cloud-fan/append.
Diffstat (limited to 'sbin/start-master.sh')
0 files changed, 0 insertions, 0 deletions