You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2014/09/21 22:06:33 UTC
[jira] [Updated] (SPARK-3595) Spark should respect configured
OutputCommitter when using saveAsHadoopFile
[ https://issues.apache.org/jira/browse/SPARK-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Wendell updated SPARK-3595:
-----------------------------------
Assignee: Ian Hummel
> Spark should respect configured OutputCommitter when using saveAsHadoopFile
> ---------------------------------------------------------------------------
>
> Key: SPARK-3595
> URL: https://issues.apache.org/jira/browse/SPARK-3595
> Project: Spark
> Issue Type: Improvement
> Affects Versions: 1.1.0
> Reporter: Ian Hummel
> Assignee: Ian Hummel
>
> When calling {{saveAsHadoopFile}}, Spark hardcodes the OutputCommitter to be a {{FileOutputCommitter}}.
> When using Spark on an EMR cluster to process and write files to/from S3, the default Hadoop configuration uses a {{DirectFileOutputCommitter}} to avoid writing to a temporary directory and doing a copy.
> Will submit a patch via GitHub shortly.
> Cheers,
--
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