You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Imran Rashid (JIRA)" <ji...@apache.org> on 2018/04/11 15:15:00 UTC

[jira] [Resolved] (SPARK-22941) Allow SparkSubmit to throw exceptions instead of exiting / printing errors.

     [ https://issues.apache.org/jira/browse/SPARK-22941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Imran Rashid resolved SPARK-22941.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 2.4.0

Issue resolved by pull request 20925
[https://github.com/apache/spark/pull/20925]

> Allow SparkSubmit to throw exceptions instead of exiting / printing errors.
> ---------------------------------------------------------------------------
>
>                 Key: SPARK-22941
>                 URL: https://issues.apache.org/jira/browse/SPARK-22941
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 2.3.0
>            Reporter: Marcelo Vanzin
>            Assignee: Marcelo Vanzin
>            Priority: Major
>             Fix For: 2.4.0
>
>
> {{SparkSubmit}} now can be called by the {{SparkLauncher}} library (see SPARK-11035). But if the caller provides incorrect or inconsistent parameters to the app, {{SparkSubmit}} will print errors to the output and call {{System.exit}}, which is not very user friendly in this code path.
> We should modify {{SparkSubmit}} to be more friendly when called this way, while still maintaining the old behavior when called from the command line.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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