[ 
https://issues.apache.org/jira/browse/AIRFLOW-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811524#comment-16811524
 ] 

ASF subversion and git services commented on AIRFLOW-4232:
----------------------------------------------------------

Commit a440e514c9e06e2601b6fe2bc747968a8a867426 in airflow's branch 
refs/heads/v1-10-test from al
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=a440e51 ]

[AIRFLOW-4232] Add `none_skipped` trigger rule (#5032)

Downstream tasks should run as long as their parents are in
`success`, `failed`, or `upstream_failed` states.


> Add a "none_skipped" trigger rule
> ---------------------------------
>
>                 Key: AIRFLOW-4232
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4232
>             Project: Apache Airflow
>          Issue Type: New Feature
>            Reporter: al
>            Assignee: al
>            Priority: Trivial
>              Labels: triggers
>             Fix For: 1.10.3
>
>
> Add a "none_skipped" trigger rule so that downstream tasks will only run if 
> _all_ theirĀ upstream tasksĀ have succeeded or failed.
> Example:
>  * Task 1 is a transform task that creates a temp table.
>  * Task 2 is a cleanup task that drops the temp table.
> Task 1 >> Task 2
> If Task 1 succeeds or fails, Task 2 should drop the temp table as cleanup. 
> However if the task never runs, we should just skip it.
> Or perhaps Task 2 is a logging task that only logs successes and failures, 
> but doesn't log skips to cut down on noise.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to