In this article, I will show you how to get an XCOM variable from another Airflow DAG.
Table of Contents
Please remember that it is not the recommended way of writing Airflow DAGs because DAGs should be independent of each other.
Airflow, however, does not stop us from using XCOM to communicate between DAGs. Here is a description of how we can do that:
- First, we need a reference to the task instance. We can get that, for example, in the PythonOperator when we set the
provide_contextparameter toTrue:
some_task = PythonOperator(
task_id='the_task_id',
python_callable=function_name,
provide_context=True,
dag=dag
)
When we do that, the function gets the DAG context as the parameter, and we can extract the task instance from the context:
def function_name(**kwargs):
task_instance = kwargs['task_instance']
- Now, we can use the
xcom_pullfunction to get the variable. Note that I have to specify both the name of the task that published the variable and the DAG identifier:
task_instance.xcom_pull(dag_id='dag_id', task_ids='task_id', key="variable_name")
There is one caveat that makes this approach almost useless. Both DAGs must have the same execution date. It is caused by the implementation of xcom_pull in the TaskInstance class. The code in the Airflow repository looks like this:
query = XCom.get_many(
execution_date=self.execution_date,
key=key,
dag_ids=dag_id,
task_ids=task_ids,
include_prior_dates=include_prior_dates,
session=session,
).with_entities(XCom.value)
Get Weekly AI Implementation Insights
Join engineering leaders who receive my analysis of common AI production failures and how to prevent them. No fluff, just actionable techniques.