Fix partitioned asset events incorrectly triggering non-partition-aware DAGs#63848
Open
ShubhamGondane wants to merge 5 commits intoapache:mainfrom
Open
Fix partitioned asset events incorrectly triggering non-partition-aware DAGs#63848ShubhamGondane wants to merge 5 commits intoapache:mainfrom
ShubhamGondane wants to merge 5 commits intoapache:mainfrom
Conversation
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.
Partitioned asset events (from DAGs using
CronPartitionTimetable) were incorrectlyqueuing non-partition-aware DAGs in
AssetDagRunQueue, causing spuriousASSET_TRIGGEREDruns. Fixed by skipping the non-partitioned queue path whenpartition_keyis set inAssetManager._queue_dagruns.closes: #63734
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Sonnet 4.6 following the guidelines