Airflow Sensor: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 6: Line 6:
* [[Airflow_Concepts#Sensor|Airflow Concepts]]
* [[Airflow_Concepts#Sensor|Airflow Concepts]]
=Overview=
=Overview=
A Sensor is a subclass of [[Airflow_Concepts#Operator|Operator]]. Sensors wait for an external event to happen. When the event they are waiting for occurs, the tasks succeeds, so their downstream tasks can run. The sensors are primarily idle, and because of that, they have primarily three modes of running, that allows executing them with various degrees of efficiency: [[#Poke|poke]], [[#Reschedule|reschedule]] and [[Smart_Sensor#smart sensors]].
A Sensor is a subclass of [[Airflow_Concepts#Operator|Operator]]. Sensors wait for an external event to happen. When the event they are waiting for occurs, the tasks succeeds, so their downstream tasks can run. The sensors are primarily idle, and because of that, they have primarily three modes of running, that allows executing them with various degrees of efficiency: [[#Poke|poke]], [[#Reschedule|reschedule]] and [[#Smart_Sensor|smart sensors]].


Also see [[Airflow_Concepts#Deferrable_Operators_and_Triggers|Deferrable Operators and Triggers]].
Also see [[Airflow_Concepts#Deferrable_Operators_and_Triggers|Deferrable Operators and Triggers]].

Revision as of 22:20, 17 July 2022

External

Internal

Overview

A Sensor is a subclass of Operator. Sensors wait for an external event to happen. When the event they are waiting for occurs, the tasks succeeds, so their downstream tasks can run. The sensors are primarily idle, and because of that, they have primarily three modes of running, that allows executing them with various degrees of efficiency: poke, reschedule and smart sensors.

Also see Deferrable Operators and Triggers.

Sensor Types

Poke

Reschedule

Smart Sensor