[jira] [Commented] (SPARK-3595) Spark should respect configured OutputCommitter when using saveAsHadoopFile

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

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

Ian Hummel commented on SPARK-3595:
-----------------------------------

PR sent: https://github.com/apache/spark/pull/2450

> 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
>
> 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