Repository navigation
Replies: 3 comments
|
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval. |
|
I'm seeing the same thing when I raise an The DAG did respect downstream trigger rules after I changed my setup task from |
|
Why can't you just add if in your operator and simply "complete". Logically speaking "Setup" and "Teardown" should ALWAYS execute. No matter if they are doing somethign or not. It's your choice to decide what setup or teardown do ( or not do) but the very basic assumption here is that they MUST complete suceessfully. Not fail, not skip, they MUST succeed. It's like in unit tests. You might want to skip the whole test (including their setup and teardown, or decide - in your setup and teardown that you do not do any setup or teardown, yet you do not change the status of setup or teardown call - they both should succeed - even if they do NOTHNG (which you can very easily do by an if that should not do stuff if it is run in environment where setting things up should not be done).. Converting to a discusion. There is no good reason to complicate setup / teardown to include addional rules here. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Apache Airflow version
2.10.5
If "Other Airflow 2 version" selected, which one?
No response
What happened?
I have created a DAG where setup task depends on branching operator (
do_start_inference).When I start it and branching operator tells that
get_job_idshould be started, andstart_servingshould be skipped, get_job_id task also skips even if it has ONE_SUCCESS trigger rule.This behaviour is only happens when using setup / teardown. If I delete
setups=start_servingfromas_teardowneverything is OK.With setup/teardown:

Without setup/teardown:

What you think should happen instead?
get_job_idshouldn't be skipped when using setup / teardownHow to reproduce
Create a DAG where setup task depends on branching operator, and run this DAG so that the branching operator goes down the branch without a setup.
Dependencies for example:
Operating System
MacOS
Versions of Apache Airflow Providers
No response
Deployment
Virtualenv installation
Deployment details
standalone
Anything else?
No response
Are you willing to submit PR?
Code of Conduct
All reactions