You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Kevin Mandich (JIRA)" <ji...@apache.org> on 2016/05/17 00:38:12 UTC

[jira] [Updated] (AIRFLOW-123) Differentiate Between Failure and Timeout

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

Kevin Mandich updated AIRFLOW-123:
----------------------------------
    Description: 
Currently, timeouts are classified as a failure (both task and DAG). It would be useful to differentiate states between a failure due to a timeout and, as an example, a failure due to an exception being raised in a PythonOperator.

At a minimum, it would be useful to see a task which failed due to timeout visualized as a different color in the Tree View. It would also nice to utilize this change as part of DAG logic. Examples here include an option to retry on timeouts specifically, and the ability to take a different action downstream if a particular task failed due to timeout.

  was:
Currently, timeouts are classified as a failure (both task and DAG). It would be useful to differentiate states between timeouts and, as an example, a failure due to an exception being raised in a PythonOperator.

At a minimum, it would be useful to see a task which failed due to timeout visualized as a different color in the Tree View. It would also nice to utilize this change as part of DAG logic. Examples here include an option to retry on timeouts specifically, and the ability to take a different action downstream if a particular task failed due to timeout.


> Differentiate Between Failure and Timeout
> -----------------------------------------
>
>                 Key: AIRFLOW-123
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-123
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: db, operators, ui
>            Reporter: Kevin Mandich
>            Priority: Minor
>
> Currently, timeouts are classified as a failure (both task and DAG). It would be useful to differentiate states between a failure due to a timeout and, as an example, a failure due to an exception being raised in a PythonOperator.
> At a minimum, it would be useful to see a task which failed due to timeout visualized as a different color in the Tree View. It would also nice to utilize this change as part of DAG logic. Examples here include an option to retry on timeouts specifically, and the ability to take a different action downstream if a particular task failed due to timeout.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)