spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <>
Subject [jira] [Updated] (SPARK-22217) ParquetFileFormat to support arbitrary OutputCommitters
Date Fri, 06 Oct 2017 16:35:00 GMT


Steve Loughran updated SPARK-22217:
    Priority: Minor  (was: Major)

> ParquetFileFormat to support arbitrary OutputCommitters
> -------------------------------------------------------
>                 Key: SPARK-22217
>                 URL:
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.2.0
>            Reporter: Steve Loughran
>            Priority: Minor
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message