[jira] [Commented] (SPARK-20937) Describe spark.sql.parquet.writeLegacyFormat property in Spark SQL, DataFrames and Datasets Guide

["Sergei (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SPARK-20937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613113#comment-16613113 ] 

Sergei commented on SPARK-20937:
--------------------------------

do you remember what did you do with it finally? 

> Describe spark.sql.parquet.writeLegacyFormat property in Spark SQL, DataFrames and Datasets Guide
> -------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-20937
>                 URL: https://issues.apache.org/jira/browse/SPARK-20937
>             Project: Spark
>          Issue Type: Improvement
>          Components: Documentation, SQL
>    Affects Versions: 2.3.0
>            Reporter: Jacek Laskowski
>            Priority: Trivial
>
> As a follow-up to SPARK-20297 (and SPARK-10400) in which {{spark.sql.parquet.writeLegacyFormat}} property was recommended for Impala and Hive, Spark SQL docs for [Parquet Files|https://spark.apache.org/docs/latest/sql-programming-guide.html#configuration] should have it documented.
> p.s. It was asked about in [Why can't Impala read parquet files after Spark SQL's write?|https://stackoverflow.com/q/44279870/1305344] on StackOverflow today.
> p.s. It's also covered in [~holden.karau@gmail.com]'s "High Performance Spark: Best Practices for Scaling and Optimizing Apache Spark" book (in Table 3-10. Parquet data source options) that gives the option some wider publicity.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org