Validate partition mapper source keys before scheduling#67119
Open
desusaiteja wants to merge 2 commits into
Open
Validate partition mapper source keys before scheduling#67119desusaiteja wants to merge 2 commits into
desusaiteja wants to merge 2 commits into
Conversation
desusaiteja
requested review from
Lee-W,
amoghrajesh,
ashb,
dstandish,
kaxil and
uranusjr
as code owners
boring-cyborg
Bot
added
area:Scheduler
potiuk
added
the
ready for maintainer review
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
2 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.
Reject non-canonical source partition keys before a partition mapper records downstream mapping for partitioned asset-triggered Dags. This keeps malformed-but-parseable keys from being normalized into incorrect target partitions, and adds regression coverage for temporal, allowed-key, product, chain, and scheduler paths.
closes: #58943
Was generative AI tooling used to co-author this PR?
Generated-by: Codex (GPT-5) following the guidelines