Airflow XComs: Difference between revisions
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
* https://airflow.apache.org/docs/apache-airflow/stable/concepts/xcoms.html | * https://airflow.apache.org/docs/apache-airflow/stable/concepts/xcoms.html | ||
* https://airflow.apache.org/docs/apache-airflow/stable/concepts/taskflow.html | * https://airflow.apache.org/docs/apache-airflow/stable/concepts/taskflow.html | ||
* https://airflow.apache.org/docs/apache-airflow/2.0.0/concepts.html#xcoms | |||
=Internal= | =Internal= | ||
Revision as of 22:56, 11 July 2022
External
- https://airflow.apache.org/docs/apache-airflow/stable/concepts/xcoms.html
- https://airflow.apache.org/docs/apache-airflow/stable/concepts/taskflow.html
- https://airflow.apache.org/docs/apache-airflow/2.0.0/concepts.html#xcoms
Internal
Overview
Tasks communicate using inputs and outputs, and XComs ("cross-communications") intermediates that.
When you call a TaskFlow function in the DAG file, rather than executing it, you will get an object representing the XCom for the result (an XComArg, that you can use as inputs to downstream tasks and operators.
Variables are an alternative mechanism for tasks to share data. However, variables are global and should be used for overall configuration that covers the entire installation. To pass data to and from tasks, XComs should be preferred instead.