🗓️Data-Aware Scheduling
Also known as Event-Driven Scheduling, Asset-Triggered Scheduling, Dataset Scheduling
A pipeline starts when its input data changes. It does not wait for a set time.
Think of it like
You eat when the food is on the table. You do not eat just because the clock says six.
Example
The orders team's load finishes at a different time each night. The finance report starts the moment it ends, never before.
Why it matters
Fixed times force you to add a safety gap. Waiting on the data itself removes the gap and the wrong reports it causes.
Definition
Example code
python
from airflow.sdk import Asset, dag
orders = Asset("s3://lake/orders")
@dag(schedule=[orders])
def build_sales_report():
...Common mistake
Key takeaways
- 1Data as the trigger. An updated table starts the next run.
- 2Across teams. Links pipelines that different people own.
- 3No guessed gaps. Runs start as soon as inputs land.