You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/25 02:33:00 UTC

[jira] [Commented] (AIRFLOW-4453) none_failed trigger rule cascading skipped state to downstream tasks

    [ https://issues.apache.org/jira/browse/AIRFLOW-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066329#comment-17066329 ] 

ASF GitHub Bot commented on AIRFLOW-4453:
-----------------------------------------

yuqian90 commented on pull request #7464: [AIRFLOW-4453] Make behavior of `none_failed` consistent with documentation
URL: https://github.com/apache/airflow/pull/7464
 
 
   This is to pick up the work started in https://github.com/apache/airflow/pull/7098. I discussed with @TV4Fun and opened this new PR to continue the work.
   
   - Make behavior of `none_failed` consistent with documentation. Do not skip itself when all parents are skipped.
   - Add `none_failed_or_skipped` which behaves like the old `none_failed` trigger rule (i.e. all parents are success or skipped and at least one parent is success). One use case of `none_failed_or_skipped` is the join task in a workflow with nested `BranchPythonOperator`
   ---
   Issue link: [AIRFLOW-4453](https://issues.apache.org/jira/browse/AIRFLOW-4453)
   
   Make sure to mark the boxes below before creating PR: [x]
   
   - [x] Description above provides context of the change
   - [x] Commit message/PR title starts with `[AIRFLOW-NNNN]`. AIRFLOW-NNNN = JIRA ID<sup>*</sup>
   - [x] Unit tests coverage for changes (not needed for documentation changes)
   - [x] Commits follow "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)"
   - [x] Relevant documentation is updated including usage instructions.
   - [x] I will engage committers as explained in [Contribution Workflow Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example).
   
   <sup>*</sup> For document-only changes commit message can start with `[AIRFLOW-XXXX]`.
   
   ---
   In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
   Read the [Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines) for more information.
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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, scheduler
>    Affects Versions: 1.10.3, 1.10.4, 1.10.5, 1.10.6, 1.10.7
>            Reporter: Dmytro Kulyk
>            Assignee: Kaxil Naik
>            Priority: Major
>              Labels: skipped
>             Fix For: 1.10.5
>
>         Attachments: 3_step.png, 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)