Etl Model With Dags And Tasks
I'm trying to model my ETL jobs with Airflow. All jobs have kind of the same structure: Extract from a transactional database(N extractions, each one reading 1/N of the table) The
Solution 1:
2nd option is better (have each sub-workflow of Company Routine
as a top-level DAG
) because
- top-level DAGs can be re-run independently (in case just one of them needs to be rerun) while you cannot rerun just a part of a DAG (if you modelled them as a monolithic DAG)
- same holds true for backfilling
But then you must link-up those top-level DAGs together too (so that they run one-after another). For that, see Wiring top-level DAGs together
Post a Comment for "Etl Model With Dags And Tasks"