Repository navigation
Conversation
antonlin1
force-pushed
the
watcher-native-partition-events
branch
from
October 23, 2026 09:57
85a6f2b to
3db227d
Compare
Partition-aware Dags cannot consume native partition scopes from watcher events when the key is retained only as payload metadata.
Watchers need to identify native partitions without adding asset-specific fields to task resumption and task-end events.
antonlin1
force-pushed
the
watcher-native-partition-events
branch
2 times, most recently
from
October 26, 2026 12:21
13041b9 to
944dce5
Compare
antonlin1
force-pushed
the
watcher-native-partition-events
branch
from
October 26, 2026 12:22
944dce5 to
3951dc9
Compare
This branch has not been deployed
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.
Problem
Currently, when an Asset watcher yields a
TriggerEvent, Airflow stores its payload in the asset event’s extra metadata.The event’s native partition_key field is left unset as
TriggerEventhas no field to distinguish it as a top level field. When Airflow prepares scheduling work for partition-aware consumers, it requires that native field. Airflow records the event but logs a missing-partition-key warning and skips creating pending partition work.Fix
Introduce
AssetTriggerEventwith an explicitpartition_key, separate from payload metadata. Preserve that key through triggerer serialization and event persistence so partition-aware Dags can schedule correctly.Was generative AI tooling used to co-author this PR?
Generated-by: Codex (GPT-6) following the guidelines