You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2015/04/14 23:09:58 UTC
[jira] [Reopened] (SPARK-6352) Supporting non-default
OutputCommitter when using saveAsParquetFile
[ https://issues.apache.org/jira/browse/SPARK-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Rosen reopened SPARK-6352:
-------------------------------
I'm re-opening this issue because I reverted the patch after it caused a test compilation failure for the Hadoop 1.x profile. Let's fix this and open a new PR.
> Supporting non-default OutputCommitter when using saveAsParquetFile
> -------------------------------------------------------------------
>
> Key: SPARK-6352
> URL: https://issues.apache.org/jira/browse/SPARK-6352
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 1.1.1, 1.2.1, 1.3.0
> Reporter: Pei-Lun Lee
> Assignee: Pei-Lun Lee
> Fix For: 1.4.0
>
>
> SPARK-3595 only handles custom OutputCommitter for saveAsHadoopFile, it can be nice to have similar behavior in saveAsParquetFile. It maybe difficult to have a fully customizable OutputCommitter solution, at least adding something like a DirectParquetOutputCommitter and letting users choose between this and the default should be enough.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org