You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be nice to have DAGs runs exit immediately after the search / download tasks is there is no products to process.
Currently this does not happen and all tasks are executed anyway. Operators should handle this gracefully as per #243 but I think would be good to have the DAGs terminate their execution early when there is nothing to process.
One way to achieve this would be to branch after the search / download and have a Dummy "finish" task by changing existing DAGs:
One possibility is to branch after the search / download and have a Dummy "finish" task:
From
Into:
Airflow may also provide other mechanisms to do this
Would be nice to have DAGs runs exit immediately after the search / download tasks is there is no products to process.
Currently this does not happen and all tasks are executed anyway. Operators should handle this gracefully as per #243 but I think would be good to have the DAGs terminate their execution early when there is nothing to process.
One way to achieve this would be to branch after the search / download and have a Dummy "finish" task by changing existing DAGs:
One possibility is to branch after the search / download and have a Dummy "finish" task:
From
Into:
Airflow may also provide other mechanisms to do this
@torse What do you think
The text was updated successfully, but these errors were encountered: