You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Cedrik Neumann (JIRA)" <ji...@apache.org> on 2019/08/10 22:24:00 UTC
[jira] [Assigned] (AIRFLOW-1784) SKIPPED status is being cascading
wrongly
[ https://issues.apache.org/jira/browse/AIRFLOW-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cedrik Neumann reassigned AIRFLOW-1784:
---------------------------------------
Assignee: Cedrik Neumann
> 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
> 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
(v7.6.14#76016)