Airflow Xcom Exclusive

This is the most critical constraint. Because XComs live in the metadata database, they are .

[core] xcom_backend = my_project.xcom_backend.ExclusiveRedisXCom

trigger = TriggerDagRunOperator( task_id="trigger_child", trigger_dag_id="child_dag", conf="xcom_passthrough": " ti.xcom_pull(task_ids='parent_task', key='authorized_key') ", )

: Stores a value in the Airflow metadata database. Many operators (and any @task function) automatically push their return value to a special key called return_value by default.

Remember: Airflow is a workflow orchestrator, not a data transport layer. Use XCom exclusively for what it does best—whispering small, critical secrets between tasks—and leave the heavy lifting to the storage and compute systems designed for it. Your future self, debugging a production DAG at 2 AM, will thank you.