[jira] [Commented] (AIRFLOW-5540) task with SparkSubmitOperator does not fail if the spark job it executes fails.

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot commented on AIRFLOW-5540:
-----------------------------------------

adankro commented on pull request #6288: AIRFLOW-5540 adding rise exception when the _resolve_connection  method fails
URL: https://github.com/apache/airflow/pull/6288
 
 
   … job it executes fails
   
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-XXX
     - In case you are fixing a typo in the documentation you can prepend your commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
     - In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)).
     - In case you are adding a dependency, check if the license complies with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
   
   ### Description
   
   - [ ] Here are some details about my PR, including screenshots of any UI changes:
   
   ### Tests
   
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use it.
     - All the public functions and the classes in the PR contain docstrings that explain what it does
     - If you implement backwards incompatible changes, please leave a note in the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so we can assign it to a appropriate release
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> task with SparkSubmitOperator  does not  fail if the  spark job it executes fails.
> ----------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-5540
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5540
>             Project: Apache Airflow
>          Issue Type: Wish
>          Components: operators
>    Affects Versions: 1.10.3
>         Environment: RHEL 7.3 with default airflow  installation.
>            Reporter: Juan M George
>            Assignee: Adan Christian Rosales Ornelas
>            Priority: Major
>         Attachments: airfow_issues
>
>
> In  my  test Dag, I have a task that uses SparkSubmitOperator operator to execute a spark job  that  reads from a table in a database and  does some processing and write into a file.   In  a scenario, where source table from where  I read data does not exist, the spark job fails but the  task  is still be shown as  executed successfully.  I don't see any other way to handle this business logic failure from the operator side.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)