[
https://issues.apache.org/jira/browse/AIRFLOW-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007203#comment-17007203
]
Joel Croteau commented on AIRFLOW-4453:
---------------------------------------
I can actually reproduce this on 1.10.3 with a much simpler DAG:
{code:java}
import datetime
from airflow.models import SkipMixin, BaseOperator, DAG
from airflow.operators.dummy_operator import DummyOperator
class SkipOperator(BaseOperator, SkipMixin):
def execute(self, context=None):
# Skip all downstream tasks
ti = context['ti']
dag_run = ti.get_dagrun()
task = ti.task
downstream_tasks = task.downstream_list
if downstream_tasks:
self.skip(dag_run, ti.execution_date, downstream_tasks)
with DAG(
schedule_interval=None,
dag_id='simple_skip',
start_date=datetime.datetime(2019, 12, 18),
) as dag:
skip_operator = SkipOperator(task_id='skip_operator')
step_1 = DummyOperator(task_id='step_1')
step_2 = DummyOperator(task_id='step_2', trigger_rule='none_failed')
skip_operator >> step_1 >> step_2
{code}
This also skips on 1.10.3. I haven't tried it in newer versions.
!simple_skip.png!
> none_failed trigger rule cascading skipped state to downstream tasks
> --------------------------------------------------------------------
>
> Key: AIRFLOW-4453
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4453
> Project: Apache Airflow
> Issue Type: Bug
> Components: DAG
> Affects Versions: 1.10.3
> Reporter: Dmytro Kulyk
> Priority: Major
> Labels: skipped
> Attachments: cube_update.py, image-2019-05-02-18-11-28-307.png,
> simple_skip.png
>
>
> Task with trigger_rule = 'none_failed' cascading *skipped *status to
> downstream task
> * task have multiple upstream tasks
> * trigger_rule set to 'none_failed'
> * some of upstream tasks can be skipped due to *latest only*
> Basing on documentation this shouldn't happen
> !image-2019-05-02-18-11-28-307.png|width=655,height=372!
> DAG attached
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
