Fix: Preserve BACKFILL run_type and triggering_user_name for repeated backfills#62142
Open
abhijeets25012-tech wants to merge 2 commits intoapache:mainfrom
Open
Fix: Preserve BACKFILL run_type and triggering_user_name for repeated backfills#62142abhijeets25012-tech wants to merge 2 commits intoapache:mainfrom
abhijeets25012-tech wants to merge 2 commits intoapache:mainfrom
Conversation
roykoand
reviewed
Feb 18, 2026
Contributor
|
Looks like static checks are failing. Please run prek locally before committing changes. |
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.
What does this PR do?
Fixes an issue where repeated backfill runs for the same logical date
could result in incorrect DagRun metadata due to IntegrityError handling
that skipped updating existing DagRuns.
Root Cause
When a DagRun already existed for a logical_date, backfill logic skipped
creation without ensuring the run_type and triggering_user_name remained
consistent with BACKFILL semantics.
Fix
When IntegrityError occurs:
Additional Notes
No new dependencies are introduced. This ensures consistent metadata
for all backfill runs, first or subsequent.
Closes: #62126