Fix misleading comment and pin reprocess behaviour for partitioned backfill#68618
Merged
Merged
Conversation
37539a9 to
c1d3616
Compare
…ckfill _create_backfill_dag_run_partitioned already created a new run when reprocess_behavior=FAILED/COMPLETED; the old comment incorrectly stated that partitioned backfills never reprocess existing runs. Adds a test to document and guard the intended behaviour (new run alongside the failed one, prior run kept as historical record).
c1d3616 to
4acf64d
Compare
uranusjr
approved these changes
Jun 17, 2026
amoghrajesh
approved these changes
Jun 17, 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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
_create_backfill_dag_run_partitionedalready created a new run whenreprocess_behavior=FAILED/COMPLETED; the old comment incorrectly stated that partitioned backfills never reprocess existing runs. Adds a test to document and guard the intended behaviour (new run alongside the failed one, prior run kept as historical record).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.