[
https://issues.apache.org/jira/browse/AIRFLOW-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986511#comment-16986511
]
ASF GitHub Bot commented on AIRFLOW-5540:
-----------------------------------------
stale[bot] commented on pull request #6288: AIRFLOW-5540 adding rise exception
when the _resolve_connection method fails
URL: https://github.com/apache/airflow/pull/6288
----------------------------------------------------------------
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:
[email protected]
> 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)
