diff options
| author | Cheng Lian <lian@databricks.com> | 2015-10-01 17:23:27 -0700 |
|---|---|---|
| committer | Yin Huai <yhuai@databricks.com> | 2015-10-01 17:23:27 -0700 |
| commit | 01cd688f5245cbb752863100b399b525b31c3510 (patch) | |
| tree | e71ac01d0ba4e58b6e7ef98759964c58ce21fa71 /unsafe/src | |
| parent | 02026a8132a2e6fe3be97b33b49826139cd1312e (diff) | |
| download | spark-01cd688f5245cbb752863100b399b525b31c3510.tar.gz spark-01cd688f5245cbb752863100b399b525b31c3510.tar.bz2 spark-01cd688f5245cbb752863100b399b525b31c3510.zip | |
[SPARK-10400] [SQL] Renames SQLConf.PARQUET_FOLLOW_PARQUET_FORMAT_SPEC
We introduced SQL option `spark.sql.parquet.followParquetFormatSpec` while working on implementing Parquet backwards-compatibility rules in SPARK-6777. It indicates whether we should use legacy Parquet format adopted by Spark 1.4 and prior versions or the standard format defined in parquet-format spec to write Parquet files.
This option defaults to `false` and is marked as a non-public option (`isPublic = false`) because we haven't finished refactored Parquet write path. The problem is, the name of this option is somewhat confusing, because it's not super intuitive why we shouldn't follow the spec. Would be nice to rename it to `spark.sql.parquet.writeLegacyFormat`, and invert its default value (the two option names have opposite meanings).
Although this option is private in 1.5, we'll make it public in 1.6 after refactoring Parquet write path. So that users can decide whether to write Parquet files in standard format or legacy format.
Author: Cheng Lian <lian@databricks.com>
Closes #8566 from liancheng/spark-10400/deprecate-follow-parquet-format-spec.
Diffstat (limited to 'unsafe/src')
0 files changed, 0 insertions, 0 deletions