Fix ingest_region_stats example Dag erroring with schedule=None#68719
Open
Lee-W wants to merge 1 commit into
Open
Fix ingest_region_stats example Dag erroring with schedule=None#68719Lee-W wants to merge 1 commit into
Lee-W wants to merge 1 commit into
Conversation
Both Dags consume runtime-partitioned assets, so they must schedule on `PartitionAtRuntime()` to be reachable; `schedule=None` and `CronPartitionTimetable` left them unrunnable. `ingest_sales` now emits the composite `region|timestamp` partitions it advertises.
Lee-W
force-pushed
the
fix-partition-example-dag-error
branch
from
c7ec0d9 to
ef16d25
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
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.
Why
A Dag consuming runtime-partitioned assets must schedule on
PartitionAtRuntime()to be reachable; `schedule=None`` left it unrunnable.What
Fix ingest_region_stats example Dag erroring with schedule=None
Was generative AI tooling used to co-author this PR?
Generated-by: [Claude] following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.