airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Davydov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AIRFLOW-904) UPSTREAM_FAILED tasks should run when their upstream task changes state
Date Fri, 24 Feb 2017 19:30:44 GMT

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

Dan Davydov updated AIRFLOW-904:
--------------------------------
    Description: 
Right now if you have a task that depends on UPSTREAM_FAILED and the UPSTREAM_FAILED task
is deleted the upstream tasks will not get kicked off.

Two ideas to solve this:
1. Get rid of the UPSTREAM_FAILED state (it can be inferred from upstream tasks), if desired
we can still color tasks in the UI based on inference
2. Make active dagruns see if UPSTREAM_FAILED every run (in case their upstream tasks changed
state).

We should be particularly careful of all of the logic in various places in the codebase that
uses the UPSTREAM_FAILED state since the new behavior could affect it.

[~bolke] [~artwr]

  was:
Right now if you have a task that depends on UPSTREAM_FAILED and the UPSTREAM_FAILED task
is deleted the upstream tasks will not get kicked off.

Two ideas to solve this:
1. Get rid of the UPSTREAM_FAILED state (it can be inferred from upstream tasks)
2. Make active dagruns see if UPSTREAM_FAILED every run (in case their upstream tasks changed
state).

We should be particularly careful of all of the logic in various places in the codebase that
uses the UPSTREAM_FAILED state since the new behavior could affect it.

[~bolke] [~artwr]


> UPSTREAM_FAILED tasks should run when their upstream task changes state
> -----------------------------------------------------------------------
>
>                 Key: AIRFLOW-904
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-904
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Dan Davydov
>
> Right now if you have a task that depends on UPSTREAM_FAILED and the UPSTREAM_FAILED
task is deleted the upstream tasks will not get kicked off.
> Two ideas to solve this:
> 1. Get rid of the UPSTREAM_FAILED state (it can be inferred from upstream tasks), if
desired we can still color tasks in the UI based on inference
> 2. Make active dagruns see if UPSTREAM_FAILED every run (in case their upstream tasks
changed state).
> We should be particularly careful of all of the logic in various places in the codebase
that uses the UPSTREAM_FAILED state since the new behavior could affect it.
> [~bolke] [~artwr]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message