Excessive XCom writes create high I/O concurrency, leading to database locks and slower scheduler loops. Designing "Exclusive" XCom Workflows
In triggered DAG:
: Rely on XCom only for small, idempotent, non-critical data. For exclusive workflows, redesign your DAG or bring your own locking mechanism.
The easiest way to generate an XCom is to return a value from an Airflow operator or a TaskFlow API function.
def push_task(**context): return "key": "value", "id": 123
Your (Astronomer, MWAA, Helm chart, Docker Compose)
task2 = BashOperator( task_id='task2', bash_command='echo task_instance.xcom_pull("greeting") ', dag=dag, )
To help tailor this guide further for your platform architecture, could you let me know: What are you currently using?
Hola ratosoci@s,
aquí encontraréis todos mis libros.
¡No os los perdáis!