[
https://issues.apache.org/jira/browse/AIRFLOW-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Potiuk closed AIRFLOW-904.
--------------------------------
Resolution: Won't Fix
I am closing some old issues that are not relevant any more. Please let me know
if you want to reopen it.
> 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
> Priority: Major
>
> 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
> (actually it might make sense to color any task that does not have it's
> dependencies met orange, although this would be very resource intensive and
> require many DB queries at the moment)
> 2. Make active dagruns see if UPSTREAM_FAILED every run (in case their
> upstream tasks changed state).
> I prefer 1) (simplifies Airflow states)
> 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
(v8.3.4#803005)
