feat(cli): support partition-date range for backfill create#67537
Draft
Lee-W wants to merge 1 commit into
Draft
Conversation
Add --partition-date-start and --partition-date-end to airflow backfill create. Bounds are inclusive calendar dates, applied as a post-filter on timetable-generated DagRunInfo for partitioned Dags. Non-partitioned Dags reject the flags; start-after-end is rejected pre-enumeration. No model columns, scheduler changes, or migrations — ordering control and independent concurrency caps from issue apache#65922 are deferred to follow-ups.
Lee-W
force-pushed
the
dags-backfill-partition-range
branch
from
ab4aec8 to
7f072b0
Compare
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add --partition-date-start and --partition-date-end to airflow backfill create. Bounds are inclusive calendar dates, applied as a post-filter on timetable-generated DagRunInfo for partitioned Dags. Non-partitioned Dags reject the flags; start-after-end is rejected pre-enumeration.
No model columns, scheduler changes, or migrations — ordering control and independent concurrency caps from issue #65922 are deferred to follow-ups.
Was generative AI tooling used to co-author this PR?
{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.