Description
When manually triggering a DAG using a temporal partitioned timetable, the trigger form leaves partition_key blank.
Submitted the form without a key created an unpartitioned DagRun. Although the run may execute successfully, its asset events cannot satisfy partition-aware downstream DAGs. This is an easy operational footgun, particularly for daily asset-driven pipelines.
Use case/motivation
Operators frequently need to manually trigger or rerun daily partitioned DAGs. Currently, they must enter the partition key manually on every trigger.
It would be useful if the form could derive a suggested key, perhaps using some custom function.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
Description
When manually triggering a DAG using a temporal partitioned timetable, the trigger form leaves partition_key blank.
Submitted the form without a key created an unpartitioned DagRun. Although the run may execute successfully, its asset events cannot satisfy partition-aware downstream DAGs. This is an easy operational footgun, particularly for daily asset-driven pipelines.
Use case/motivation
Operators frequently need to manually trigger or rerun daily partitioned DAGs. Currently, they must enter the partition key manually on every trigger.
It would be useful if the form could derive a suggested key, perhaps using some custom function.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct