What is Apache Airflow - Complexity Analysis

Time Complexity: What is Apache Airflow

O(n)

Understanding Time Complexity

We want to understand how the time it takes to run Apache Airflow tasks changes as we add more tasks or workflows.

How does Airflow handle more work, and how does that affect execution time?

Scenario Under Consideration

Analyze the time complexity of a simple Airflow DAG that runs multiple tasks sequentially.

from airflow import DAG
from airflow.operators.python import PythonOperator
from datetime import datetime

def task_function():
    print("Task executed")

dag = DAG('simple_dag', start_date=datetime(2024, 1, 1))

tasks = []
for i in range(5):
    task = PythonOperator(task_id=f'task_{i}', python_callable=task_function, dag=dag)
    tasks.append(task)

for i in range(4):
    tasks[i] >> tasks[i+1]

This code creates a DAG with 5 tasks that run one after another.

Identify Repeating Operations

Look for loops or repeated actions in the code.

• Primary operation: Creating and linking tasks in a loop.
• How many times: The loop runs 5 times to create tasks, and 4 times to link them.

How Execution Grows With Input

As the number of tasks (n) increases, the number of operations to create and link tasks grows roughly the same.

Input Size (n)	Approx. Operations
10	About 19 (10 create + 9 link)
100	About 199 (100 create + 99 link)
1000	About 1999 (1000 create + 999 link)

Pattern observation: Operations grow roughly in a straight line as tasks increase.

Final Time Complexity

Time Complexity: O(n)

This means the time to set up tasks grows directly with the number of tasks.

Common Mistake

[X] Wrong: "Adding more tasks will make setup time grow much faster, like squared or exponential."

[OK] Correct: Each task is created and linked once, so the work grows evenly, not faster.

Interview Connect

Understanding how Airflow scales with tasks helps you explain workflow efficiency and resource planning in real projects.

Self-Check

"What if tasks were linked in a more complex pattern, like every task depending on all previous tasks? How would the time complexity change?"

Practice

1. What is the main purpose of Apache Airflow?

easy

A. To monitor network traffic

B. To store large amounts of data

C. To create user interfaces for websites

D. To automate and schedule tasks in a specific order

Solution

1. Step 1: Understand Apache Airflow's role

   Apache Airflow is designed to automate and schedule tasks, not to store data or create interfaces.

2. Step 2: Identify the correct purpose

   It manages workflows by running tasks in a defined order automatically.

3. Final Answer:

   To automate and schedule tasks in a specific order -> Option D

4. Quick Check:

   Automation and scheduling = A [OK]

Hint: Airflow schedules and runs tasks automatically [OK]

Common Mistakes:

• Confusing Airflow with data storage tools
• Thinking Airflow builds websites
• Assuming Airflow monitors networks

2. Which of the following is the correct way to define a DAG in Apache Airflow using Python?

easy

A. dag = DAG('my_dag', schedule_interval='@daily')

B. dag = DAG('my_dag' schedule_interval='@daily')

C. dag = DAG['my_dag', schedule_interval='@daily']

D. dag = DAG{'my_dag', schedule_interval='@daily'}

Solution

1. Step 1: Check Python syntax for function calls

   Function calls use parentheses with arguments separated by commas.

2. Step 2: Identify correct syntax

   dag = DAG('my_dag', schedule_interval='@daily') uses parentheses and commas correctly; others have missing commas or wrong brackets.

3. Final Answer:

   dag = DAG('my_dag', schedule_interval='@daily') -> Option A

4. Quick Check:

   Function call syntax = A [OK]

Hint: Use parentheses and commas for function arguments [OK]

Common Mistakes:

• Missing commas between arguments
• Using square or curly brackets instead of parentheses
• Incorrect argument separation

3. Given the following Airflow DAG snippet, what will be the order of task execution?

from airflow import DAG
from airflow.operators.dummy import DummyOperator
from datetime import datetime

dag = DAG('example_dag', start_date=datetime(2023,1,1))

t1 = DummyOperator(task_id='task1', dag=dag)
t2 = DummyOperator(task_id='task2', dag=dag)
t3 = DummyOperator(task_id='task3', dag=dag)

t1 >> t2 >> t3

medium

A. All tasks run at the same time

B. task3 runs, then task2, then task1

C. task1 runs, then task2, then task3

D. task2 runs first, then task1, then task3

Solution

1. Step 1: Understand the '>>' operator in Airflow

   The '>>' operator sets task dependencies, meaning left task runs before right task.

2. Step 2: Trace the task order

   t1 >> t2 >> t3 means task1 runs first, then task2, then task3.

3. Final Answer:

   task1 runs, then task2, then task3 -> Option C

4. Quick Check:

   Dependency chain = task1 -> task2 -> task3 [OK]

Hint: The '>>' operator means 'runs before' [OK]

Common Mistakes:

• Thinking tasks run in reverse order
• Assuming tasks run in parallel without dependencies
• Misreading the '>>' operator

4. You wrote this Airflow DAG code but it fails to run:

from airflow import DAG
from airflow.operators.dummy import DummyOperator
from datetime import datetime

dag = DAG('my_dag', start_date=datetime(2023,1,1))

t1 = DummyOperator(task_id='task1')
t2 = DummyOperator(task_id='task2')

t1 >> t2

What is the error?

medium

A. Task IDs must be integers

B. Missing DAG parameter in DummyOperator tasks

C. start_date must be a string

D. Wrong import for DummyOperator

Solution

1. Step 1: Check task definitions

   Tasks need to be linked to a DAG by passing the 'dag' parameter.

2. Step 2: Identify missing 'dag' argument

   t1 and t2 are missing 'dag=dag', so Airflow doesn't know which DAG they belong to.

3. Final Answer:

   Missing DAG parameter in DummyOperator tasks -> Option B

4. Quick Check:

   Tasks need DAG assigned = D [OK]

Hint: Always assign tasks to a DAG with dag=dag [OK]

Common Mistakes:

• Forgetting to pass dag=dag to tasks
• Incorrect imports causing errors
• Wrong data types for start_date or task_id

5. You want to create an Airflow workflow that retries a task up to 3 times if it fails. Which DAG task parameter should you set?

hard

A. retries=3

B. retry_count=3

C. max_retry=3

D. retry_limit=3

Solution

1. Step 1: Recall Airflow retry parameter

   Airflow uses 'retries' to specify how many times to retry a failed task.

2. Step 2: Match parameter name

   The correct parameter is 'retries', not retry_count, max_retry, or retry_limit.

3. Final Answer:

   retries=3 -> Option A

4. Quick Check:

   Retries parameter controls retry count = B [OK]

Hint: Use 'retries' to set retry attempts in Airflow tasks [OK]

Common Mistakes:

• Using incorrect parameter names like retry_count
• Confusing retry count with timeout
• Not setting retries at all