spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Ash (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-3595) Spark should respect configured OutputCommitter when using saveAsHadoopFile
Date Fri, 12 Dec 2014 18:54:13 GMT

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

Andrew Ash commented on SPARK-3595:
-----------------------------------

Hi [~pwendell], with the past couple months of indirect testing in master, how do you feel
about riskiness of backporting into 1.1 ?  [~mccheah] and I are interested.

> 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
>             Fix For: 1.2.0
>
>
> 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


Mime
View raw message