GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/8566
[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).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/liancheng/spark
spark-10400/deprecate-follow-parquet-format-spec
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/8566.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #8566
----
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
