You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2022/02/04 16:14:00 UTC

[jira] [Commented] (SPARK-38102) Supporting custom commitProtocolClass when using saveAsNewAPIHadoopDataset

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

Apache Spark commented on SPARK-38102:
--------------------------------------

User 'ocworld' has created a pull request for this issue:
https://github.com/apache/spark/pull/35397

> Supporting custom commitProtocolClass when using saveAsNewAPIHadoopDataset
> --------------------------------------------------------------------------
>
>                 Key: SPARK-38102
>                 URL: https://issues.apache.org/jira/browse/SPARK-38102
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 3.2.0
>            Reporter: Keunhyun Oh
>            Priority: Major
>
> There is no way to apply spark-hadoop-cloud's commitProtocolClass when using saveAsNewAPIHadoopDataset that are to avoid object storage's problem.
> [https://spark.apache.org/docs/latest/cloud-integration.html]
>  
> It is needed to support custom commitProtocolClass class when using saveAsNewAPIHadoopDataset by an option. For example,
> {code:java}
> spark.hadoop.mapreduce.sources.commitProtocolClass org.apache.spark.internal.io.cloud.PathOutputCommitProtocol{code}
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org