Sharing data between tasks effectively in Apache Airflow - Time & Space Complexity

Time Complexity: Sharing data between tasks effectively

O(n)

Understanding Time Complexity

When tasks share data in Airflow, the way data is passed affects how long the workflow takes to run.

We want to know how the time to share data grows as the amount of data or number of tasks increases.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

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

def push_data(ti):
    data = list(range(1000))
    ti.xcom_push(key='my_data', value=data)

def pull_data(ti):
    data = ti.xcom_pull(key='my_data', task_ids='push_task')
    print(len(data))

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

push_task = PythonOperator(task_id='push_task', python_callable=push_data, dag=dag)
pull_task = PythonOperator(task_id='pull_task', python_callable=pull_data, dag=dag)
push_task >> pull_task

This code pushes a list of 1000 numbers from one task and pulls it in another using XComs.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Creating and transferring a list of data items between tasks.
• How many times: The list size determines how many items are handled; here 1000 items.

How Execution Grows With Input

As the data size grows, the time to push and pull data grows roughly in proportion to the number of items.

Input Size (n)	Approx. Operations
10	Handles 10 data items
100	Handles 100 data items
1000	Handles 1000 data items

Pattern observation: Doubling the data roughly doubles the work to share it.

Final Time Complexity

Time Complexity: O(n)

This means the time to share data grows linearly with the amount of data passed between tasks.

Common Mistake

[X] Wrong: "Sharing data between tasks is always instant and does not depend on data size."

[OK] Correct: Actually, larger data means more time to serialize, transfer, and deserialize, so it takes longer.

Interview Connect

Understanding how data sharing scales helps you design workflows that run smoothly and predictably as they grow.

Self-Check

"What if we changed from passing data via XCom to using an external database? How would the time complexity change?"

Practice

1. What is the primary purpose of using Airflow Variables when sharing data between tasks?

easy

A. To execute tasks in parallel

B. To monitor task execution logs

C. To schedule DAG runs automatically

D. To store small pieces of data accessible across different tasks

Solution

1. Step 1: Understand Airflow Variables role

   Airflow Variables are designed to hold small data values that can be shared between tasks.

2. Step 2: Identify the correct use case

   Sharing data between tasks requires a storage mechanism accessible by all tasks, which Airflow Variables provide.

3. Final Answer:

   To store small pieces of data accessible across different tasks -> Option D

4. Quick Check:

   Airflow Variables = data sharing [OK]

Hint: Variables store shared data between tasks easily [OK]

Common Mistakes:

• Confusing Variables with task scheduling
• Thinking Variables execute tasks
• Using Variables for logging

2. Which of the following is the correct way to set an Airflow Variable named my_var with value 123 inside a PythonOperator task?

easy

A. Variable.set('my_var', 123)

B. Variable.set(my_var, '123')

C. Variable.get('my_var', 123)

D. Variable.create('my_var', 123)

Solution

1. Step 1: Recall Variable.set syntax

   The correct method to set a variable is Variable.set(key, value) where key is a string and value is the data.

2. Step 2: Check option correctness

   Variable.set('my_var', 123) uses Variable.set with key 'my_var' and value 123 correctly as a string key and integer value.

3. Final Answer:

   Variable.set('my_var', 123) -> Option A

4. Quick Check:

   Set variable = Variable.set(key, value) [OK]

Hint: Use Variable.set('key', value) to store data [OK]

Common Mistakes:

• Using Variable.get instead of set to store data
• Not quoting the variable name key
• Using a non-existent method like Variable.create

3. Given the following code snippet in two tasks, what will be printed by task_b?

from airflow.models import Variable

def task_a():
    Variable.set('shared_key', 'hello')

def task_b():
    value = Variable.get('shared_key')
    print(value)

medium

A. None

B. hello

C. shared_key

D. Error: Variable not found

Solution

1. Step 1: Analyze task_a behavior

   task_a sets the Variable 'shared_key' with value 'hello'.

2. Step 2: Analyze task_b behavior

   task_b retrieves the Variable 'shared_key' and prints its value, which is 'hello'.

3. Final Answer:

   hello -> Option B

4. Quick Check:

   Set then get Variable = 'hello' [OK]

Hint: Get returns the stored value by key [OK]

Common Mistakes:

• Expecting the key name instead of value
• Assuming Variable.get returns None if set
• Forgetting to set the Variable before getting

4. You wrote this code in task_b to get a Variable set by task_a:

value = Variable.get('my_var')

But you get an error: KeyError: 'Variable my_var does not exist'. What is the best fix?

medium

A. Set a default value in Variable.get like Variable.get('my_var', default_var='default')

B. Change Variable.get to Variable.set

C. Remove the Variable.get call

D. Restart Airflow scheduler

Solution

1. Step 1: Understand the error cause

   The error means 'my_var' was not set before getting it, so Variable.get fails.

2. Step 2: Use default value to avoid error

   Variable.get supports a default_var parameter to return if key missing, preventing KeyError.

3. Final Answer:

   Set a default value in Variable.get like Variable.get('my_var', default_var='default') -> Option A

4. Quick Check:

   Use default_var to avoid missing key error [OK]

Hint: Add default_var to Variable.get to prevent errors [OK]

Common Mistakes:

• Using Variable.set instead of get to read data
• Ignoring missing Variable errors
• Restarting scheduler without fixing code

5. You want to share a list of user IDs between two tasks in Airflow. Which approach is best to share this data effectively?

hard

A. Write the list to a local file and read it in the next task

B. Pass the list directly as a Python variable between tasks

C. Use XComs to push and pull the list between tasks

D. Serialize the list as JSON string and store it in an Airflow Variable

Solution

1. Step 1: Understand data sharing options

   Airflow Variables are for small strings; passing Python variables directly is not possible between tasks.

2. Step 2: Identify best practice for complex data

   XComs are designed to share data like lists between tasks efficiently and safely.

3. Final Answer:

   Use XComs to push and pull the list between tasks -> Option C

4. Quick Check:

   XComs = best for task-to-task data sharing [OK]

Hint: Use XComs for complex data sharing between tasks [OK]

Common Mistakes:

• Trying to pass Python variables directly
• Using Variables for large or complex data
• Using local files which break portability