Airflow Xcom Exclusive -

When we talk about "exclusive" XCom usage, we refer to the practice of restricting data access to specific tasks or ensuring that only certain keys are utilized to avoid "polluting" the metadata database. 1. Avoiding Database Bloat

: While primarily used within one DAG, xcom_pull can be configured with a different dag_id to retrieve values from an entirely separate workflow, provided you have the correct execution date or use include_prior_dates=True . Critical Limitations XComs — Airflow 3.2.1 Documentation airflow xcom exclusive

t1 >> t2 >> t3

: When using the TaskFlow API (introduced in Airflow 2.0), simply returning a value from a decorated python function automatically pushes it to XCom as a return_value . The Essential Rule: Keep it Lightweight When we talk about "exclusive" XCom usage, we

The modern TaskFlow API simplifies data passing. When you return a value from a decorated @task , Airflow creates an implicit connection. : You don't manually call xcom_pull . Critical Limitations XComs — Airflow 3

from airflow.decorators import dag, task from datetime import datetime