The GitHub Actions job "Check newsfragment PR number" on airflow.git/partition-key-fallback-noncron has succeeded. Run started by GitHub user Lee-W (triggered by Lee-W).
Head commit for run: e50b39e7c765e1852781271404be5c3f0b247611 / Wei Lee <[email protected]> Pre-fill a suggested partition key when manually triggering asset-driven or runtime partitioned Dags The manual-trigger form's partition key field is empty for asset-driven (PartitionedAssetTimetable) and partitioned_at_runtime Dags, since neither type has a natural schedule tick to derive a value from. Submitting without a key creates an unpartitioned run, which asset-driven downstream Dags can never satisfy. This adds a best-effort suggestion, tried in order: a pending AssetPartitionDagRun already waiting on this Dag, a purely time-based guess from the timetable's own asset partition mappers, and finally the partition key of the most recent successful run. The suggestion only pre-fills the UI field; validate_partition_key still accepts None, and users can edit or clear the field before submitting. The partitioned_at_runtime type's partition key field was also not rendered at all in the trigger form, even though the backend already accepts a partition_key for it; this fixes that visibility gap alongside the suggestion feature. Track 1 of the same issue (#71284) adds the same base class method (Timetable.suggest_partition_key) and the same two DAGResponse fields (suggested_partition_key, timetable_partitioned_at_runtime) for the Cron timetable case, as a parallel, not-yet-merged PR. This PR temporarily duplicates those declarations so it can be developed independently; once Track 1 merges, this PR should be rebased to drop the duplicated base class method and API field declarations, keeping only the asset-driven and runtime-specific fallback logic, resolver, and UI/tests. Report URL: https://github.com/apache/airflow/actions/runs/31447202252 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
