Uh oh!
There was an error while loading. Please reload this page.
Fix airflow partitions clear date range for non-UTC partitioned timetables - #68460
Merged
Merged
Conversation
Lee-Wforce-pushed
the
fix-partitions-clear-timezone
branch
from
June 12, 2026 23:33
17d4f0e to
f2cdaa7CompareLee-Wforce-pushed
the
fix-partitions-clear-timezone
branch
from
June 15, 2026 09:02
f2cdaa7 to
7095eddCompareLee-W
marked this pull request as ready for review
June 15, 2026 09:04
Lee-Wforce-pushed
the
fix-partitions-clear-timezone
branch
from
June 15, 2026 09:04
7095edd to
b160f90Compareuranusjr
approved these changes
Jun 15, 2026
…ables Resolve start/end bounds through the Dag timetable's timezone via `resolve_day_bound`, mirroring the fix applied to `airflow dags clear` in apache#67717. Switch from closed `<=` to half-open `< upper` range semantics. Without this fix, a date-only input like "2026-02-19" is compared directly as UTC midnight, causing the run stored at 2026-02-18T16:00Z (local midnight in Asia/Taipei) to be silently missed or incorrectly included.
Lee-Wforce-pushed
the
fix-partitions-clear-timezone
branch
from
June 15, 2026 10:47
b160f90 to
f6e1b9bCompareUh oh!
There was an error while loading. Please reload this page.
pgagnon pushed a commit
to pgagnon/airflow
that referenced
this pull request
Jun 15, 2026
imrichardwu pushed a commit
to imrichardwu/airflow
that referenced
this pull request
Jun 16, 2026
dingo4dev pushed a commit
to dingo4dev/airflow
that referenced
this pull request
Jun 16, 2026
RulerChen pushed a commit
to RulerChen/airflow
that referenced
this pull request
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
airflow dags clearin #67717 didn't consider the timetable's timezone.Without this fix, a date-only input like "2026-02-19" is compared directly as UTC midnight, causing the run stored at
2026-02-18T16:00Z(local midnight in Asia/Taipei) to be silently missed or incorrectly included.What
Resolve start/end bounds through the Dag timetable's timezone via
resolve_day_bound. Switch from closed<=to half-open< upperrange semantics.Was generative AI tooling used to co-author this PR?
Generated-by: [Claude] following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.