Airflow Xcom Exclusive !!top!! — No Survey

[core] xcom_backend = my_project.xcom_backend.ExclusiveRedisXCom

For true data isolation or to handle sensitive/large data "exclusively" outside the Airflow DB: airflow xcom exclusive

| Issue | Consequence | |-------|--------------| | DB becomes bottleneck | Many large XComs slow down scheduler | | Not designed for streaming | Only final values, not incremental | | No automatic cleanup (unless configured) | XCom rows accumulate | | Cross-DAG XCom is fragile | Requires manual conf passing | [core] xcom_backend = my_project

Tasks interact with XComs through two main methods on the TaskInstance object: airflow xcom exclusive

By default, XCom allows to write to any key, and any task to read from any key. This creates several issues: