amoghrajesh commented on issue #49540: URL: https://github.com/apache/airflow/issues/49540#issuecomment-2820666846
Hello @kosteev i have responded to you over email. But reiterating for others: Yes, this change was intentional in Airflow 3. Here’s why: 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 this inconsistency by requiring task_ids when pulling by key. This change aligns with the task-scoped nature of XComs as defined by the schema, ensuring predictable and consistent behavior. We will be fixing this in a later patch release but to answer your question, it is an intended change and is being handled in migration guide via the PR: https://github.com/apache/airflow/pull/49455 -- 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]
