Add asset partition sensor#67941
Draft
Leondon9 wants to merge 2 commits into
Draft
Conversation
e0b2c41 to
5b85614
Compare
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.
Add a small server-side partition lookup for asset events and a standard provider sensor that can wait for a specific asset partition from a time-scheduled DAG.
What changed:
This is intended as a narrow draft for the idea in #67375. It deliberately avoids broader pattern/regex filters, Core API expansion, DB migrations/indexes, UI changes, and generated OpenAPI churn. It overlaps with part of #64610 only in the exact partition lookup surface; if #64610 lands first, this branch should be rebased and the lookup commit can likely be dropped or reduced.
Validation:
Pytest was attempted with Breeze, but the local test bootstrap failed before collecting/running the changed tests due provider discovery/import setup issues (airflow.providers.akeyless) and task_sdk import setup in the container.
related: #67375
Was generative AI tooling used to co-author this PR?
Generated-by: Codex (GPT-5) following https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions