You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2018/12/06 14:58:00 UTC
[jira] [Resolved] (AIRFLOW-1490) In order to get details on
exceptions thrown by tasks, the onfailure callback needs an enhancement
[ https://issues.apache.org/jira/browse/AIRFLOW-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ash Berlin-Taylor resolved AIRFLOW-1490.
----------------------------------------
Resolution: Duplicate
AIRFLOW-843 merged and in 1.10.1 release
> In order to get details on exceptions thrown by tasks, the onfailure callback needs an enhancement
> --------------------------------------------------------------------------------------------------
>
> Key: AIRFLOW-1490
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1490
> Project: Apache Airflow
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.8.0, 2.0.0
> Reporter: Steen Manniche
> Priority: Major
> Attachments: 0001-AIRFLOW-1490-carry-exceptions-through-to-the-on_fail.patch
>
>
> The code called when an exception is thrown by a task receives information on the exception thrown from the task, but fails to delegate this information to the registered callbacks.
> https://github.com/apache/incubator-airflow/blob/master/airflow/models.py#L1524 sends the context to the registered failure callback, but this context does not include the thrown exception.
> The supplied patch proposes a non-api-breaking way of including the exception in the context in order to provide clients with the full exception type and -traceback
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)