You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/02/01 20:43:32 UTC
[GitHub] [airflow] joetsx commented on issue #19222: none_failed_min_one_success trigger rule not working with BranchPythonOperator in certain cases.
joetsx commented on issue #19222:
URL: https://github.com/apache/airflow/issues/19222#issuecomment-1027268949
> Seeing the same issue with BranchPythonOperator / branching and the final task (i.e. task6) being incorrectly skipped instead of being called. This is observed in 2.2.x but not in 2.1.x and not in 2.0.x To be specific, this is unrelated to returning an "empty" task ID, as we're seeing this happen even when the task ID is returned.
In the attached DAG example, tasks{1,2,3} are long running, and fast_task{1,2} get completed fast. The problem happens with fast_task2_x - which trigger rule is set to "none_failed_or_skipped" - but it is getting incorrectly skipped in version 2.2.3 but not in 2.0.1 and not in 2.1.2. This incorrect skipping behavior seem to happen with more complex dependencies, and appears to be broken starting 2.2.x
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org