-
Notifications
You must be signed in to change notification settings - Fork 16.5k
Open
Labels
affected_version:2.0Issues Reported for 2.0Issues Reported for 2.0affected_version:3.0Issues Reported for 3.0Issues Reported for 3.0area:backfillSpecifically for backfill relatedSpecifically for backfill relatedarea:corekind:metaHigh-level information important to the communityHigh-level information important to the communitypriority:lowBug with a simple workaround that would not block a releaseBug with a simple workaround that would not block a release
Description
Body
With a timedelta-scheduled dag, the logical dates that you get are relative to the start-date you provide when running the backfill command.
This has been the behavior since 2.x
So, e.g. suppose your dag has schedule of timedelta(days=1). Then, running this
airflow dags backfill test_backfill_dag__timedelta --start-date '2025-03-10 03:25:26' --end-date 2025-03-13 --dry-run
Will produce these runs:
"2025-03-10 03:25:26+00:00"
"2025-03-11 03:25:26+00:00"
"2025-03-12 03:25:26+00:00"
But if the schedule was cron schedule, then it would be what you would expect -- just the "partitions" that are within the range requested.
Committer
- I acknowledge that I am a maintainer/committer of the Apache Airflow project.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
affected_version:2.0Issues Reported for 2.0Issues Reported for 2.0affected_version:3.0Issues Reported for 3.0Issues Reported for 3.0area:backfillSpecifically for backfill relatedSpecifically for backfill relatedarea:corekind:metaHigh-level information important to the communityHigh-level information important to the communitypriority:lowBug with a simple workaround that would not block a releaseBug with a simple workaround that would not block a release