[
https://issues.apache.org/jira/browse/AIRFLOW-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024171#comment-17024171
]
ASF subversion and git services commented on AIRFLOW-1784:
----------------------------------------------------------
Commit b568f745a9882a51cb63ca226edfc30021c7c1fc in airflow's branch
refs/heads/master from Cedrik Neumann
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=b568f74 ]
[AIRFLOW-2923][AIRFLOW-1784] Implement LatestOnlyOperator as BaseBranchOperator
(#5970)
LatestOnlyOperator is a special case of a BranchOperator, thus it should
inherit from it.
This fixes an issue where the skipping behaviour of LatestOnlyOperator is
inconsistent with other operators,
by forcefully skipping all downstream tasks recursively ignoring trigger rules.
> SKIPPED status is being cascading wrongly
> -----------------------------------------
>
> Key: AIRFLOW-1784
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1784
> Project: Apache Airflow
> Issue Type: Bug
> Components: operators
> Affects Versions: 1.8.2
> Environment: Ubuntu 16.04.3 LTS
> Python 2.7.12
> CeleryExecutor: 2-nodes cluster
> Reporter: Dmytro Kulyk
> Assignee: Cedrik Neumann
> Priority: Critical
> Labels: documentation, latestonly, operators
> Fix For: 2.0.0
>
> Attachments: Capture_graph.JPG, Capture_tree2.JPG, cube_update.py
>
>
> After implementation of AIRFLOW-1296 within 1.8.2 there is an wrong behavior
> of LatestOnlyOperator which is forcing SKIPPED status cascading despite of
> TriggerRule='all_done' set
> Which is opposite to documented
> [here|https://airflow.incubator.apache.org/concepts.html#latest-run-only]
> *Expected Behavior:*
> dummy task and all downstreams (update_*) should not be skipped
> Full listings are attached
> 1.8.1 did not have such issue
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
