kaxil commented on code in PR #49455: URL: https://github.com/apache/airflow/pull/49455#discussion_r2053729538
########## RELEASE_NOTES.rst: ########## @@ -331,6 +331,26 @@ The internal representation of asset event triggers now also includes an explici aligning with the broader asset-aware execution model introduced in Airflow 3.0. DAG authors interacting directly with ``inlet_events`` may need to update logic that assumes the previous structure. + +Predictable Behaviour of ``xcom_pull`` +"""""""""""""""""""""""""""""""""""""" + +In Airflow 2, the xcom_pull() method allowed pulling XComs by key without specifying task_ids, despite the fact that the underlying +DB model defines task_id as part of the XCom primary key. This created ambiguity: if two tasks pushed XComs with the same key, +xcom_pull() would pull whichever one happened to be first, leading to unpredictable behavior. + +Airflow 3 resolves im inconsistency by requiring task_ids when pulling by key. This change aligns with the task-scoped nature of Review Comment: ```suggestion Airflow 3 resolves im inconsistency by requiring ``task_ids`` when pulling by key. This change aligns with the task-scoped nature of ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
