You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "L. C. Hsieh (Jira)" <ji...@apache.org> on 2020/10/16 17:01:00 UTC
[jira] [Resolved] (SPARK-33167) Throw Spark specific exception for
commit protocol errors
[ https://issues.apache.org/jira/browse/SPARK-33167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
L. C. Hsieh resolved SPARK-33167.
---------------------------------
Resolution: Not A Problem
> Throw Spark specific exception for commit protocol errors
> ---------------------------------------------------------
>
> Key: SPARK-33167
> URL: https://issues.apache.org/jira/browse/SPARK-33167
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.1.0
> Reporter: L. C. Hsieh
> Assignee: L. C. Hsieh
> Priority: Major
>
> In SPARK-29649, we catch `FileAlreadyExistsException` in `FileFormatWriter` and fail fast for the task set to prevent task retry.
> One concern for this approach is we might break some cases where users rely on task retry and their tasks throw `FileAlreadyExistsException` in user code, instead of Spark internally.
> To take care both cases, better approach is to throw a Spark specific exception for commit protocol errors.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org