The GitHub Actions job "Tests (AMD)" on airflow.git/fix/partition-key-semantics-67368 has failed. Run started by GitHub user bramhanandlingala (triggered by potiuk).
Head commit for run: a4deec938536f06b03814990e5088690d7c3d9a9 / = <[email protected]> fix: clarify partition_key semantics across DagRun, AssetEvent, and runtime Three related fixes to make partition_key semantics consistent and well-defined across the Airflow partition feature (AIP-76): 1. Remove DagRun back-fill from task-emitted outlet events. A task emitting a single distinct partition_key no longer silently writes it back to DagRun.partition_key. The DagRun key is set at trigger time and is the authoritative source; tasks should not overwrite it. 2. Extra-only outlet events inherit dag_run.partition_key. When a task emits an outlet event with no explicit partition_key (only extra data), the event now inherits the DagRun-level partition_key instead of storing None. This makes provenance consistent regardless of whether the event has runtime keys or not. 3. Warn when add_partitions() is called on an asset alias accessor. Partition keys set via OutletEventAccessor.add_partitions() on an alias have no effect because aliases do not propagate partition keys. A UserWarning is now raised to guide authors toward using the target asset accessor directly. 4. Reject partition_key at REST API trigger for non-partitioned DAGs. POST /dags/{dag_id}/dagRuns now returns HTTP 400 when partition_key is supplied but the DAG timetable does not support partitions, preventing silently-ignored keys being stored on a run that can never use them. Fixes: #67368 Report URL: https://github.com/apache/airflow/actions/runs/26370326121 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
