[jira] [Updated] (SPARK-22217) ParquetFileFormat to support arbitrary OutputCommitters

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

     [ https://issues.apache.org/jira/browse/SPARK-22217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran updated SPARK-22217:
-----------------------------------
    Summary: ParquetFileFormat to support arbitrary OutputCommitters  (was: ParquetFileFormat to support arbitrary OutputCommitters if parquet.enable.summary-metadata is false)

> ParquetFileFormat to support arbitrary OutputCommitters
> -------------------------------------------------------
>
>                 Key: SPARK-22217
>                 URL: https://issues.apache.org/jira/browse/SPARK-22217
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.2.0
>            Reporter: Steve Loughran
>
> Although you can choose which committer to write dataframes as parquet data via {{spark.sql.parquet.output.committer.class}}, you get a class cast exception if this is not a {{org.apache.parquet.hadoop.ParquetOutputCommitter}} or subclass.
> This is not consistent with the docs in SQLConf, which says
> bq.  The specified class needs to be a subclass of org.apache.hadoop.mapreduce.OutputCommitter.  Typically, it's also a subclass of org.apache.parquet.hadoop.ParquetOutputCommitter.
> It is simple to relax {{ParquetFileFormat}}'s requirements, though if the user has set
> {{parquet.enable.summary-metadata=true}}, and set a committer which is not a ParquetOutputCommitter, then they won't see the data.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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