Atomic operations in pipelines in Apache Airflow - Mini Project: Build & Apply

Atomic operations in pipelines

📖 Scenario: You are managing a data pipeline using Apache Airflow. You want to ensure that a critical operation in your pipeline runs atomically, meaning it either completes fully or does not run at all. This prevents partial updates that could cause errors downstream.

🎯 Goal: Build a simple Airflow DAG that performs an atomic operation using a Python function. The DAG should have a task that updates a shared variable only if a condition is met, simulating an atomic update.

📋 What You'll Learn

Create a Python dictionary called shared_data with initial values.

Add a configuration variable update_key to specify which key to update.

Write a Python function atomic_update that updates shared_data atomically if the key exists.

Create an Airflow DAG with a PythonOperator that runs atomic_update.

Print the updated shared_data after the task runs.

💡 Why This Matters

🌍 Real World

In real data pipelines, atomic operations prevent partial updates that can cause inconsistent data or errors. Using Airflow to manage these operations helps keep pipelines reliable and maintainable.

💼 Career

Understanding atomic operations and how to implement them in Airflow is important for data engineers and DevOps professionals who build and maintain robust data workflows.

1

Create initial shared data dictionary

Create a Python dictionary called shared_data with these exact entries: 'counter': 0, 'status': 'pending'.

Apache Airflow

# Create the shared_data dictionary with initial values
# Your code here

Hint

Use curly braces to create a dictionary and include the keys 'counter' and 'status' with the specified values.

2

Add configuration variable for update key

Add a variable called update_key and set it to the string 'counter'.

Apache Airflow

shared_data = {'counter': 0, 'status': 'pending'}
# Add the update_key variable below
# Your code here

Hint

Simply assign the string 'counter' to the variable update_key.

3

Write atomic update function

Write a function called atomic_update that takes no arguments and updates shared_data[update_key] by adding 1 only if update_key exists in shared_data. Use an if statement to check the key.

Apache Airflow

shared_data = {'counter': 0, 'status': 'pending'}
update_key = 'counter'

# Define the atomic_update function below
# Your code here

Hint

Define a function with def. Use if update_key in shared_data: to check the key, then increment the value.

4

Create Airflow DAG and run atomic update

Create an Airflow DAG named atomic_dag with a single PythonOperator task called update_task that runs the atomic_update function. Then, print the shared_data dictionary after the task runs.

Apache Airflow

shared_data = {'counter': 0, 'status': 'pending'}
update_key = 'counter'

def atomic_update():
    if update_key in shared_data:
        shared_data[update_key] += 1

# Import Airflow modules and create DAG with PythonOperator
# Your code here

Hint

Import DAG and PythonOperator. Define the DAG with dag_id='atomic_dag'. Create update_task to run atomic_update. Execute the task and print shared_data.

Practice

1. What does it mean for a task in an Airflow pipeline to be atomic?

easy

A. The task can be skipped without affecting the pipeline

B. The task runs multiple times in parallel

C. The task either completes fully or does not change anything at all

D. The task runs only once per day

Solution

1. Step 1: Understand atomicity in pipelines

   Atomic means an operation is indivisible: it either fully happens or not at all.

2. Step 2: Apply this to Airflow tasks

   In Airflow, atomic tasks ensure no partial changes if they fail.

3. Final Answer:

   The task either completes fully or does not change anything at all -> Option C

4. Quick Check:

   Atomic = all or nothing [OK]

Hint: Atomic means all or nothing for task completion [OK]

Common Mistakes:

• Thinking atomic means running multiple times
• Confusing atomic with task scheduling frequency
• Assuming atomic means task can be skipped

2. Which of the following is the correct way to define a PythonOperator task in Airflow to ensure atomicity?

easy

A. task = PythonOperator(task_id='task1', python_callable=my_func, retry=3)

B. task = PythonOperator(task_id='task1', python_callable=my_func, retries='three')

C. task = PythonOperator(task_id='task1', python_callable=my_func, retry_count=3)

D. task = PythonOperator(task_id='task1', python_callable=my_func, retries=3)

Solution

1. Step 1: Check PythonOperator parameters

   The correct parameter for retry attempts is retries with an integer value.

2. Step 2: Validate each option

   task = PythonOperator(task_id='task1', python_callable=my_func, retries=3) uses retries=3 correctly. Options A, B, and D use wrong parameter names or types.

3. Final Answer:

   task = PythonOperator(task_id='task1', python_callable=my_func, retries=3) -> Option D

4. Quick Check:

   Correct retries param = task = PythonOperator(task_id='task1', python_callable=my_func, retries=3) [OK]

Hint: Use 'retries' with integer for retry count [OK]

Common Mistakes:

• Using string instead of integer for retries
• Using incorrect parameter names like retry or retry_count
• Missing retries parameter for retry logic

3. Given this Airflow task code snippet, what will be the output if my_task fails on first try but succeeds on retry?

task = PythonOperator(
    task_id='my_task',
    python_callable=my_func,
    retries=1,
    retry_delay=timedelta(seconds=5)
)

medium

A. Task fails and pipeline stops immediately

B. Task retries once after 5 seconds and then succeeds

C. Task retries infinitely until success

D. Task skips retry and marks success

Solution

1. Step 1: Understand retries and retry_delay

   Retries=1 means one retry attempt after failure, retry_delay=5 seconds means wait 5 seconds before retry.

2. Step 2: Apply to task behavior

   If first try fails, Airflow waits 5 seconds and retries once. If retry succeeds, task is marked success.

3. Final Answer:

   Task retries once after 5 seconds and then succeeds -> Option B

4. Quick Check:

   Retries=1 means one retry attempt [OK]

Hint: Retries=1 means one retry after delay [OK]

Common Mistakes:

• Assuming no retry happens
• Thinking retries means infinite retries
• Ignoring retry_delay effect

4. You wrote a task that updates a database but sometimes leaves partial updates if it fails. What is the best way to fix this atomicity issue?

medium

A. Add database transactions inside the task to commit or rollback changes

B. Increase the task timeout to avoid failures

C. Remove retries to prevent repeated partial updates

D. Split the task into multiple smaller tasks without transactions

Solution

1. Step 1: Identify cause of partial updates

   Partial updates happen if database changes are not atomic, meaning no transaction control.

2. Step 2: Apply database transactions

   Using transactions ensures all changes commit together or rollback on failure, fixing atomicity.

3. Final Answer:

   Add database transactions inside the task to commit or rollback changes -> Option A

4. Quick Check:

   Transactions ensure atomic DB updates [OK]

Hint: Use DB transactions to ensure all-or-nothing updates [OK]

Common Mistakes:

• Thinking increasing timeout fixes atomicity
• Removing retries causes no atomicity improvement
• Splitting tasks without transactions still risks partial updates

5. You want to ensure a pipeline task that writes files to cloud storage is atomic. Which approach best guarantees no partial files remain if the task fails?

hard

A. Write files to a temporary location first, then move them to final location after success

B. Write files directly to final location and delete on failure manually

C. Write files without retries to avoid duplicates

D. Write files in parallel to speed up the task

Solution

1. Step 1: Understand atomic file writes

   Writing directly risks partial files if failure occurs mid-write.

2. Step 2: Use temporary location and move

   Writing to temp location then moving is atomic because move is usually instant and atomic, avoiding partial files in final location.

3. Final Answer:

   Write files to a temporary location first, then move them to final location after success -> Option A

4. Quick Check:

   Temp write + move = atomic file update [OK]

Hint: Write temp files then move to final location atomically [OK]

Common Mistakes:

• Writing directly risks partial files
• Deleting on failure is error-prone
• Skipping retries does not guarantee atomicity
• Parallel writes do not ensure atomic single file