Airflow Concepts: Difference between revisions
Jump to navigation
Jump to search
(→SubDAG) |
|||
| Line 16: | Line 16: | ||
Tasks have dependencies on each other. | Tasks have dependencies on each other. | ||
==<span id='Dependency'></span>Task Dependencies== | ==<span id='Dependency'></span>Task Dependencies== | ||
If a task B has a dependency on task A (A → B), it is said that A is upstream of B and B is downstream of A. | |||
==Task Types== | ==Task Types== | ||
===Operator=== | ===Operator=== | ||
Revision as of 01:34, 11 July 2022
External
Internal
Workflow
DAG
SubDAG
A DAG is made of tasks among which there are relations of dependency. The DAG is not concerned about what happens inside the tasks, it is only concerned about how to run them: order, retries, timeouts. etc.
Task
Tasks have dependencies on each other.
Task Dependencies
If a task B has a dependency on task A (A → B), it is said that A is upstream of B and B is downstream of A.
Task Types
Operator
Sensor
A Sensor is a subclass of Operator.
TaskFlow-decorated Task
Passing Data between Tasks
Tasks pass data among each other using:
- XComs, when the amount of metadata to be exchanged is small.
- Uploading and downloading large files from a storage service.
TaskGroup
XComs
"Cross-communications".