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
Thanks for a really awesome demo of how to integrate dbt with airflow. We use airflow extensively and generate multiple DAGs, one for each functional area (marketing, finance, etc.). While we try to keep the DAGs as independent as possible, realistically, there are always a few cross-dag dependencies that we handle using ExternalTaskSensor. Is it possible to handle it within this architecture?
I tried to add tags to the tasks for each DAG. However, except for staging instantiating the DAG with dbt_tag resulted in a DAG with empty dbt_run and dbt_test task groups. Intuitively, here is what I am thinking should work:
Use tags to identify separate DAGs.
While processing a specific DAG, generate wait_for tasks using ExternalSensor for dependencies that are NOT in the same DAG.
I would love to get your thoughts on the best way to operationalize this.
The text was updated successfully, but these errors were encountered:
Thanks for a really awesome demo of how to integrate
dbt
withairflow
. We useairflow
extensively and generate multiple DAGs, one for each functional area (marketing, finance, etc.). While we try to keep the DAGs as independent as possible, realistically, there are always a few cross-dag dependencies that we handle usingExternalTaskSensor
. Is it possible to handle it within this architecture?I tried to add tags to the tasks for each DAG. However, except for
staging
instantiating the DAG withdbt_tag
resulted in a DAG with emptydbt_run
anddbt_test
task groups. Intuitively, here is what I am thinking should work:wait_for
tasks usingExternalSensor
for dependencies that are NOT in the same DAG.I would love to get your thoughts on the best way to operationalize this.
The text was updated successfully, but these errors were encountered: