[
https://issues.apache.org/jira/browse/AIRFLOW-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024170#comment-17024170
]
ASF subversion and git services commented on AIRFLOW-2923:
----------------------------------------------------------
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.
> LatestOnlyOperator cascade skip through all_done and dummy
> ----------------------------------------------------------
>
> Key: AIRFLOW-2923
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2923
> Project: Apache Airflow
> Issue Type: Bug
> Components: scheduler
> Affects Versions: 1.9.0, 1.10.5, 1.10.6, 1.10.7
> Environment: CeleryExecutor, 2-nodes cluster, RMQ, PostgreSQL
> Reporter: Dmytro Kulyk
> Assignee: Cedrik Neumann
> Priority: Major
> Labels: cascade, latestonly, skip
> Fix For: 2.0.0
>
> Attachments: cube_update.py, screenshot-1.png
>
>
> DAG with consolidating point (calc_ready : dummy)
> as per [https://airflow.apache.org/concepts.html#latest-run-only] given task
> should be ran even catching up an execution DagRuns for a previous periods
> However, LatestOnlyOperator cascading through calc_ready despite of it is a
> dummy and trigger_rule=all_done, none_failed
> Same behavior when trigger_rule=all_success
> {code}
> t_ready = DummyOperator(
> task_id = 'calc_ready',
> trigger_rule = TriggerRule.ALL_DONE,
> dag=dag)
> {code}
> !screenshot-1.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
