Orchestrating dbt with Airflow - Time & Space Complexity

Time Complexity: Orchestrating dbt with Airflow

O(n)

Understanding Time Complexity

When using Airflow to run dbt tasks, it's important to understand how the total time grows as you add more dbt models or steps.

We want to know how the orchestration time changes when the number of dbt tasks increases.

Scenario Under Consideration

Analyze the time complexity of this Airflow DAG running dbt models sequentially.

from airflow import DAG
from airflow.operators.bash import BashOperator
from datetime import datetime

def create_dbt_task(model_name, dag):
    return BashOperator(
        task_id=f'dbt_run_{model_name}',
        bash_command=f'dbt run --models {model_name}',
        dag=dag
    )

dag = DAG('dbt_sequential', start_date=datetime(2024,1,1))
models = ['model1', 'model2', 'model3', 'model4']

previous_task = None
for model in models:
    task = create_dbt_task(model, dag)
    if previous_task:
        previous_task >> task
    previous_task = task

This code runs dbt models one after another in Airflow, waiting for each to finish before starting the next.

Identify Repeating Operations

Look at what repeats as the input grows.

• Primary operation: Running each dbt model as a separate Airflow task.
• How many times: Once per model, so the number of tasks equals the number of models.

How Execution Grows With Input

As you add more dbt models, the total time grows because each model runs one after another.

Input Size (n)	Approx. Operations
10	10 dbt runs, one after another
100	100 dbt runs, sequentially
1000	1000 dbt runs, sequentially

Pattern observation: The total time grows roughly in direct proportion to the number of models.

Final Time Complexity

Time Complexity: O(n)

This means the total orchestration time grows linearly as you add more dbt models to run one after another.

Common Mistake

[X] Wrong: "Running multiple dbt models in Airflow always happens at the same time, so time stays the same no matter how many models."

[OK] Correct: In this setup, models run one after another, so adding more models adds more total time.

Interview Connect

Understanding how task orchestration time grows helps you design workflows that scale well and keep pipelines efficient.

Self-Check

What if we changed the Airflow DAG to run all dbt models in parallel instead of sequentially? How would the time complexity change?

Practice

1. What is the main purpose of using Airflow with dbt in data workflows?

easy

A. To automate and schedule dbt commands in a specific order

B. To replace dbt's SQL models with Python scripts

C. To visualize dbt models as charts

D. To manually run dbt commands from the command line

Solution

1. Step 1: Understand Airflow's role

   Airflow is a tool to automate and schedule tasks, including dbt commands.

2. Step 2: Connect Airflow with dbt

   Using Airflow, you can run dbt commands automatically and in order without manual intervention.

3. Final Answer:

   To automate and schedule dbt commands in a specific order -> Option A

4. Quick Check:

   Airflow automates dbt runs = C [OK]

Hint: Airflow schedules tasks; dbt runs models. Together automate workflows [OK]

Common Mistakes:

• Thinking Airflow replaces dbt's SQL modeling
• Confusing manual and automated runs
• Assuming Airflow visualizes dbt models

2. Which Airflow operator is commonly used to run dbt commands inside a DAG?

easy

A. BashOperator

B. PythonOperator

C. HttpOperator

D. EmailOperator

Solution

1. Step 1: Identify how dbt commands run

   dbt commands run in the shell or terminal, so Airflow needs an operator that runs shell commands.

2. Step 2: Match operator to shell commands

   BashOperator runs bash shell commands, perfect for running dbt CLI commands inside Airflow.

3. Final Answer:

   BashOperator -> Option A

4. Quick Check:

   BashOperator runs shell commands = A [OK]

Hint: Use BashOperator for shell commands like dbt runs [OK]

Common Mistakes:

• Choosing PythonOperator which runs Python code, not shell commands
• Confusing HttpOperator with web requests
• Thinking EmailOperator runs commands

3. Given this Airflow DAG snippet, what is the order of task execution?

dbt_run = BashOperator(task_id='dbt_run', bash_command='dbt run')
dbt_test = BashOperator(task_id='dbt_test', bash_command='dbt test')
dbt_run >> dbt_test

medium

A. dbt_run and dbt_test run in parallel

B. dbt_run runs first, then dbt_test

C. dbt_test runs first, then dbt_run

D. Only dbt_test runs

Solution

1. Step 1: Understand the dependency operator

   The '>>' operator in Airflow means the left task runs before the right task.

2. Step 2: Apply to given tasks

   dbt_run >> dbt_test means dbt_run runs first, then dbt_test runs after it finishes.

3. Final Answer:

   dbt_run runs first, then dbt_test -> Option B

4. Quick Check:

   dbt_run >> dbt_test means run then test = A [OK]

Hint: >> means left task runs before right task [OK]

Common Mistakes:

• Thinking >> means parallel execution
• Reversing the order of tasks
• Assuming only one task runs

4. Identify the error in this Airflow task setup for running dbt tests:

dbt_test = BashOperator(task_id='dbt_test', bash_command='dbt test')
dbt_test.set_upstream('dbt_run')

medium

A. bash_command should be a list, not a string

B. task_id cannot be 'dbt_test'

C. set_upstream expects a task object, not a string

D. BashOperator cannot run dbt commands

Solution

1. Step 1: Check set_upstream usage

   set_upstream expects another task object, not a string task id.

2. Step 2: Identify correct usage

   It should be dbt_test.set_upstream(dbt_run) where dbt_run is the task object, not 'dbt_run' string.

3. Final Answer:

   set_upstream expects a task object, not a string -> Option C

4. Quick Check:

   set_upstream needs task object = B [OK]

Hint: set_upstream needs task object, not string name [OK]

Common Mistakes:

• Passing string instead of task object to set_upstream
• Thinking bash_command must be a list
• Believing task_id has naming restrictions
• Assuming BashOperator can't run dbt

5. You want to create an Airflow DAG that runs dbt run, then dbt test, and finally sends an email notification only if tests pass. Which sequence correctly sets task dependencies?

hard

A. dbt_run >> email_notify >> dbt_test

B. email_notify >> dbt_run >> dbt_test

C. dbt_test >> dbt_run >> email_notify

D. dbt_run >> dbt_test >> email_notify

Solution

1. Step 1: Define correct task order

   First, run models with dbt run, then test them with dbt test, and finally notify if tests pass.

2. Step 2: Set dependencies accordingly

   Use '>>' to chain tasks in order: dbt_run >> dbt_test >> email_notify.

3. Final Answer:

   dbt_run >> dbt_test >> email_notify -> Option D

4. Quick Check:

   Run then test then notify = D [OK]

Hint: Chain tasks in order with >>: run, test, then notify [OK]

Common Mistakes:

• Placing email notification before tests
• Reversing run and test order
• Skipping dependencies causing parallel runs