[
https://issues.apache.org/jira/browse/AIRFLOW-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fokko Driesprong reassigned AIRFLOW-3823:
-----------------------------------------
Assignee: Bas Harenslak
> Exclude BranchPythonOperator branch's downstream tasks from the tasks to skip
> -----------------------------------------------------------------------------
>
> Key: AIRFLOW-3823
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3823
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Bas Harenslak
> Assignee: Bas Harenslak
> Priority: Major
> Attachments: Greenshot 2019-02-07 19.48.16.png, Greenshot 2019-02-07
> 20.48.54.png, image-2019-02-07-16-45-07-900.png,
> image-2019-02-07-16-50-15-163.png
>
>
> I encountered this edge case where one of the BranchPythonOperator's options
> was a downstream task of another option. This resulted in the task being
> skipped, even though it was eligible to be run as normal (depending on your
> definition of "normal" - either prefer to run all downstream tasks of the
> chosen task, or either prefer to skip any task that is not chosen). For
> example:
> !image-2019-02-07-16-45-07-900.png!
> t4 is an option of the branch task, but also a downstream task of t1. IMO it
> shouldn't be skipped.
> I see several options:
> # hack around by adding dummy task between branch - t4 and set
> TriggerRule.ONE_SUCCESS for t4 (and educate people to do this....)
> # throw exception and don't allow this
> # when creating the list of tasks to skip, exclude tasks that are downstream
> tasks of the selected task
> I opt for option #3 and will create PR for this, resulting in:
> !image-2019-02-07-16-50-15-163.png!
> Branch task completed successfully and selected t1, but since t4 is one of
> its downstream tasks, it wasn't skipped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
