Replies: 2 comments 4 replies
-
|
I guess we can set schedule interval to None to make it run only one instance if __name__ == '__main__':
dag.schedule_interval = None
dag.clear()
dag.run()But but calling |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
another related question .... why does it conver sensors to be reschedule mode? i tried DE with a sensor and it does not seem to respect the poke interval but seems to poke as fast as it can... |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I tried out DebugExecutor with the test dag pasted below.
It created 3 runs of the dag. And also curiously it uses the backfill system.
This seems like pretty undesirable behavior. Usually if you're trying to test a dag end-to-end, you will want to run just a single dag run. And dealing with task state and backfills... when you're debugging something you just want it to run so I'm not sure why we do this.
Is there a better cleaner way to use debug executor, or to run a dag in the way I'm looking for?
For example, something that behaves like this would make more sense to me:
But it would be better if I did not have to manually specify task sequence, and better still if everything that ordinarily would go to airflow logs would instead be printed to stdout.
What do you think? @turbaszek I think you are author of this executor... you have any thoughts or advice?
Thanks
Test dag:
Beta Was this translation helpful? Give feedback.
All reactions