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
I am looking for a way to use asset-aware scheduling for our DAGs. We have several processes that load various assets (database records) for a particular date. Other DAGs should run as soon as these records are available, where typically such a DAG needs more than one of such a source asset. To get consistent data, those sources need to be linked to the same calendar day and we should only run if all assets for a particular day are present.
Maybe taking this example:
We have two DAGs, producing assets A and B. They should normally run once a day, but it might happen that one runs twice or that one of them fails.
DAG C (or a task within) needs both assets A and B. It should run immediately after A and B are loaded for the logical day.
So, given the scenario: A runs once, B runs twice. The A event and the first B event are consumed. Fine. The next day, we get an A event but B (for the new day) is not ready yet. We have to ensure that Airflow waits for the B event of today, even if there is one left from yesterday.
What is the recommended way in Airflow 3 to handle this scenario, where multiple assets must be aligned by partition before a consumer DAG should run?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello community,
I am looking for a way to use asset-aware scheduling for our DAGs. We have several processes that load various assets (database records) for a particular date. Other DAGs should run as soon as these records are available, where typically such a DAG needs more than one of such a source asset. To get consistent data, those sources need to be linked to the same calendar day and we should only run if all assets for a particular day are present.
Maybe taking this example:
So, given the scenario: A runs once, B runs twice. The A event and the first B event are consumed. Fine. The next day, we get an A event but B (for the new day) is not ready yet. We have to ensure that Airflow waits for the B event of today, even if there is one left from yesterday.
What is the recommended way in Airflow 3 to handle this scenario, where multiple assets must be aligned by partition before a consumer DAG should run?
Beta Was this translation helpful? Give feedback.
All reactions