DAG parsing and import errors in Apache Airflow - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the DAG class from Airflow.

Apache Airflow

from airflow.[1] import DAG

Drag options to blanks, or click blank then click option'

Aoperators

Bhooks

Cmodels

Dutils

Attempts:

3 left

💡 Hint

Common Mistakes

Importing DAG from the wrong module causes import errors during DAG parsing.

The DAG class is located in the airflow.models module, so importing it from there is correct.

2fill in blank

medium

Complete the code to define the DAG's start date using Airflow's datetime utility.

Apache Airflow

from airflow.utils.dates import [1]

start_date = [1](1)

Drag options to blanks, or click blank then click option'

Adays_ago

Bdatetime

Ctimedelta

Dtimezone

Attempts:

3 left

💡 Hint

Common Mistakes

Using Python's standard datetime instead of Airflow's utility can cause timezone problems.

The days_ago function is used to set relative start dates in Airflow DAGs, which helps avoid timezone issues.

3fill in blank

hard

Fix the error in the DAG import statement to avoid parsing errors.

Apache Airflow

from airflow.operators.bash import [1]Operator

bash_task = [1]Operator(task_id='print_date', bash_command='date')

Drag options to blanks, or click blank then click option'

Abash

BBash

CBashOperator

Dbashoperator

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase or incorrect casing causes import or attribute errors.

The correct class name is BashOperator with uppercase B and O. The import path uses bash module but the class name must be exact.

4fill in blank

hard

Fill both blanks to correctly define a DAG with a daily schedule and a default argument for retries.

Apache Airflow

default_args = {'retries': [1]
dag = DAG('example_dag', default_args=default_args, schedule_interval=[2])

Drag options to blanks, or click blank then click option'

A1

B'@daily'

C'@hourly'

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using 0 retries disables retries, which might not be desired.

Using wrong schedule strings causes DAG not to run as expected.

Setting retries to 1 means the task will retry once on failure. The schedule_interval '@daily' runs the DAG every day.

5fill in blank

hard

Fill all three blanks to create a task using PythonOperator with a callable function and assign it to the DAG.

Apache Airflow

def my_task():
    print('Hello Airflow')

from airflow.operators.python import [1]
task = [1](task_id=[2], python_callable=[3], dag=dag)

Drag options to blanks, or click blank then click option'

APythonOperator

B'my_task'

Cmy_task

D'print_hello'

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the function name in quotes for python_callable causes errors.

Using incorrect task_id strings or missing dag parameter causes DAG parsing failures.

The PythonOperator runs Python functions. The task_id is a string identifier, here 'print_hello'. The python_callable is the function my_task defined above.

Practice

1. What happens when Airflow encounters a DAG parsing error?

easy

A. Airflow stops reading the DAG and does not schedule it

B. Airflow ignores the error and schedules the DAG anyway

C. Airflow automatically fixes the error and reloads the DAG

D. Airflow deletes the DAG file from the folder

Solution

1. Step 1: Understand DAG parsing in Airflow

   DAG parsing means Airflow reads your workflow files to build task graphs.

2. Step 2: Effect of parsing errors

   If there is a parsing error, Airflow cannot read the DAG and stops scheduling it.

3. Final Answer:

   Airflow stops reading the DAG and does not schedule it -> Option A

4. Quick Check:

   DAG parsing error = DAG not scheduled [OK]

Hint: Parsing errors stop DAG scheduling immediately [OK]

Common Mistakes:

• Thinking Airflow ignores parsing errors
• Assuming Airflow auto-fixes code errors
• Believing DAG files get deleted automatically

2. Which of the following is the correct way to import a module in an Airflow DAG file?

easy

A. from airflow.operators.bash_operator import BashOperator

B. import airflow.operators.bash_operator

C. import BashOperator from airflow.operators.bash_operator

D. include airflow.operators.bash_operator

Solution

1. Step 1: Recall Python import syntax

   The correct Python syntax to import a class is 'from module import Class'.

2. Step 2: Match with Airflow import style

   Airflow DAGs use 'from airflow.operators.bash_operator import BashOperator' to import operators.

3. Final Answer:

   from airflow.operators.bash_operator import BashOperator -> Option A

4. Quick Check:

   Correct Python import syntax = from airflow.operators.bash_operator import BashOperator [OK]

Hint: Use 'from module import Class' for Airflow operators [OK]

Common Mistakes:

• Using 'include' instead of 'import'
• Wrong import order like 'import Class from module'
• Importing whole module without needed classes

3. Given this DAG snippet, what error will Airflow show during parsing?

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

default_args = {'start_date': datetime(2023, 1, 1)}

dag = DAG('example_dag', default_args=default_args)

t1 = BashOperator(task_id='print_date', bash_command='date', dag=dag)

print(t1)

medium

A. ImportError: No module named 'airflow.operators.bash_operator'

B. TypeError: DAG() missing required positional argument 'schedule_interval'

C. No error, DAG parses successfully

D. SyntaxError: invalid syntax in DAG definition

Solution

1. Step 1: Check DAG instantiation parameters

   The DAG constructor requires 'dag_id' and 'default_args'. 'schedule_interval' is optional and defaults to null.

2. Step 2: Verify imports and syntax

   All imports are correct and syntax is valid. BashOperator is properly used with 'dag=dag'.

3. Final Answer:

   No error, DAG parses successfully -> Option C

4. Quick Check:

   Valid imports and parameters = No error [OK]

Hint: Check if required DAG args are present; schedule_interval is optional [OK]

Common Mistakes:

• Assuming schedule_interval is mandatory
• Confusing import paths for operators
• Missing dag parameter in operator

4. You see this error in Airflow logs: ModuleNotFoundError: No module named 'pandas' when parsing a DAG. What is the best way to fix it?

medium

A. Remove all pandas imports from the DAG file

B. Rename the DAG file to avoid parsing

C. Restart Airflow scheduler without changes

D. Install pandas in the Airflow environment using pip

Solution

1. Step 1: Understand the error cause

   ModuleNotFoundError means Python cannot find the 'pandas' package in the environment.

2. Step 2: Fix by installing missing package

   Install pandas using 'pip install pandas' in the Airflow environment to resolve the import error.

3. Final Answer:

   Install pandas in the Airflow environment using pip -> Option D

4. Quick Check:

   Missing module error = install package [OK]

Hint: Install missing Python packages to fix import errors [OK]

Common Mistakes:

• Ignoring missing package errors
• Restarting without installing packages
• Deleting or renaming DAG files unnecessarily

5. You have a DAG file that imports a custom Python module located in /opt/airflow/custom_modules/my_module.py. Airflow shows an import error during DAG parsing. What is the best way to fix this?

hard

A. Move the custom module inside the DAGs folder

B. Add /opt/airflow/custom_modules to the PYTHONPATH environment variable

C. Rename the module to avoid import conflicts

D. Remove the import statement from the DAG file

Solution

1. Step 1: Identify cause of import error

   Airflow cannot find the custom module because its folder is not in Python's search path.

2. Step 2: Fix by adding module path to PYTHONPATH

   Adding the custom module folder to PYTHONPATH lets Python locate and import it during DAG parsing.

3. Final Answer:

   Add /opt/airflow/custom_modules to the PYTHONPATH environment variable -> Option B

4. Quick Check:

   Custom module import error = add folder to PYTHONPATH [OK]

Hint: Add custom module folder to PYTHONPATH for imports [OK]

Common Mistakes:

• Moving modules without updating imports
• Removing imports instead of fixing paths
• Renaming modules without reason