Execution date vs logical date in Apache Airflow - Quick Revision & Key Differences

Recall & Review

beginner

What is the start date in Airflow?

The start date is the timestamp when Airflow schedules a task or DAG to start running. It represents the earliest time the task is eligible to run.

beginner

What does the logical date mean in Airflow?

The logical date is the scheduled time for which the task or DAG run is responsible. It represents the data interval or period the run is processing.

intermediate

How do start date and logical date differ in Airflow?

Start date is when the task is scheduled to run, while logical date is the scheduled time the task run represents. Logical date is often earlier than start date.

intermediate

Why is the logical date important in Airflow scheduling?

Logical date helps Airflow know which data period the task run is processing, enabling correct data partitioning and backfilling.

advanced

If a DAG is scheduled daily at midnight, what would be the logical date and start date for the run at 2024-06-02 00:00?

Logical date: 2024-06-01 00:00 (the data day being processed). Start date: 2024-06-02 00:00 (when the task actually runs).

In Airflow, what does the logical date represent?

A The time the DAG was created

B The actual time the task starts running

C The scheduled time the task run is responsible for

D The time the task finished

Logical date is the scheduled time or data interval the task run processes.

Which date is usually earlier in Airflow: start date or logical date?

A Logical date

B Depends on the DAG

C They are always the same

D Start date

Logical date is usually earlier because it represents the data period before the task runs.

If a DAG runs daily at midnight, what is the logical date for the run at 2024-06-10 00:00?

A 2024-06-09 00:00

B 2024-06-10 00:00

C 2024-06-11 00:00

D The current system time

Logical date is the start of the data interval, so for the run at midnight June 10, it is June 9.

Why does Airflow use logical dates instead of just start dates?

A To log the system time

B To know when the task finished

C To schedule the next run

D To track the data interval the task processes

Logical dates help Airflow manage data intervals and backfills correctly.

Which of these is true about start date in Airflow?

A It is the time the task run is scheduled for

B It is the time the task actually starts running

C It is always earlier than logical date

D It is the time the DAG was last modified

Start date is when the task actually runs, not when it is scheduled.

Explain the difference between start date and logical date in Airflow.

Think about when the task runs versus what data it processes.

Why is understanding logical date important when scheduling DAGs in Airflow?

Consider how Airflow knows which data to work on.

Practice

1. What does the logical date in Airflow represent?

easy

A. The time period the task is processing data for

B. The exact time the task started running

C. The current system time when the task runs

D. The time when the DAG was created

Solution

1. Step 1: Understand the definition of logical date

   The logical date is the timestamp representing the data interval the task is working on, not when it runs.

2. Step 2: Differentiate from execution date

   Execution date is when the task actually runs, but logical date points to the data period it processes.

3. Final Answer:

   The time period the task is processing data for -> Option A

4. Quick Check:

   Logical date = data period [OK]

Hint: Logical date = data period, execution date = run time [OK]

Common Mistakes:

• Confusing logical date with actual run time
• Thinking logical date is current system time
• Mixing execution date with DAG creation time

2. Which of the following is the correct way to access the logical date inside an Airflow task?

easy

A. Using context['execution_date']

B. Using context['logical_date']

C. Using context['run_time']

D. Using context['start_date']

Solution

1. Step 1: Recall Airflow context variables

   Airflow provides logical_date in the context to represent the logical date of the task instance.

2. Step 2: Identify the correct key for logical date

   The key 'logical_date' is used to access the logical date, while 'execution_date' is deprecated in newer versions.

3. Final Answer:

   Using context['logical_date'] -> Option B

4. Quick Check:

   Access logical date with context['logical_date'] [OK]

Hint: Use context['logical_date'] for logical date in Airflow 2.2+ [OK]

Common Mistakes:

• Using deprecated 'execution_date' key
• Trying to access logical date with 'run_time'
• Confusing start_date with logical date

3. Given a DAG scheduled daily at midnight, if a task runs on 2024-06-10 00:00 UTC, what is its logical date?

medium

A. 2024-06-10 00:00 UTC

B. 2024-06-11 00:00 UTC

C. 2024-06-09 00:00 UTC

D. The current system time when the task runs

Solution

1. Step 1: Understand daily scheduling in Airflow

   A DAG scheduled daily at midnight runs for the data of the previous day, so the logical date is the start of that previous day.

2. Step 2: Calculate logical date for run on 2024-06-10 00:00 UTC

   The run at midnight on June 10 processes data for June 9, so logical date is 2024-06-09 00:00 UTC.

3. Final Answer:

   2024-06-09 00:00 UTC -> Option C

4. Quick Check:

   Run time = June 10, logical date = June 9 [OK]

Hint: Logical date is previous day for daily midnight runs [OK]

Common Mistakes:

• Assuming logical date equals execution date
• Using current system time as logical date
• Confusing next day as logical date

4. You see a task's logs showing execution_date as 2024-06-10 but the data processed is from 2024-06-11. What is the likely issue?

medium

A. The task is running twice for the same data

B. The DAG schedule interval is set to hourly instead of daily

C. The system clock is incorrect

D. The task is using execution_date instead of logical_date for data filtering

Solution

1. Step 1: Analyze mismatch between execution_date and data date

   If data processed is from a later date than execution_date, the task likely uses execution_date (run time) instead of logical_date (data period) for filtering.

2. Step 2: Understand correct usage of logical date

   Logical date should be used to select data for the intended period; using execution_date causes off-by-one errors.

3. Final Answer:

   The task is using execution_date instead of logical_date for data filtering -> Option D

4. Quick Check:

   Use logical_date for data period, not execution_date [OK]

Hint: Use logical_date for data filtering, not execution_date [OK]

Common Mistakes:

• Ignoring difference between execution and logical dates
• Assuming schedule interval causes date mismatch
• Blaming system clock without checking code

5. You want to process hourly data with a DAG scheduled every hour. The task should process data for the previous hour. Which date should you use inside the task to filter data correctly?

hard

A. Use logical_date which represents the data interval start

B. Use DAG start_date

C. Use current system time when the task runs

D. Use execution_date which is the task run time

Solution

1. Step 1: Understand hourly scheduling and data processing

   For hourly DAGs, the logical date marks the start of the hour for which data is processed, typically the previous hour.

2. Step 2: Choose the correct date for filtering data

   Using logical_date ensures the task filters data for the correct hour interval, not the actual run time.

3. Final Answer:

   Use logical_date which represents the data interval start -> Option A

4. Quick Check:

   Hourly data uses logical_date for correct filtering [OK]

Hint: For hourly data, always use logical_date for filtering [OK]

Common Mistakes:

• Using execution_date causes off-by-one hour errors
• Using current time ignores schedule intervals
• Confusing DAG start_date with data interval