Airflow Xcom Exclusive -

In practice, an XCom Exclusive looks like this: a task generates a unique resource identifier (e.g., a S3 key, a BigQuery table name, a Spark application ID). It pushes only that string . Downstream tasks then use that string to interact with the external system directly.

April 8, 2026

An treats XCom as a read-only, immutable, single-purpose reference , never as a payload carrier. The word "exclusive" implies three constraints: airflow xcom exclusive

In modern Airflow versions (2.0+), you can configure . This allows you to store XCom data in external systems like S3, GCS, Azure Blob Storage, or HDFS rather than the Airflow database. In practice, an XCom Exclusive looks like this: