airflow.sensors.external_task_sensor

Module Contents

class airflow.sensors.external_task_sensor.ExternalTaskSensor(external_dag_id, external_task_id=None, allowed_states=None, execution_delta=None, execution_date_fn=None, check_existence=False, *args, **kwargs)[source]

Bases: airflow.sensors.base_sensor_operator.BaseSensorOperator

Waits for a different DAG or a task in a different DAG to complete for a specific execution_date

Parameters

  • external_dag_id (str) – The dag_id that contains the task you want to wait for

  • external_task_id (str or None) – The task_id that contains the task you want to wait for. If None (default value) the sensor waits for the DAG

  • allowed_states (list) – list of allowed states, default is ['success']

  • execution_delta (datetime.timedelta) – time difference with the previous execution to look at, the default is the same execution_date as the current task or DAG. For yesterday, use [positive!] datetime.timedelta(days=1). Either execution_delta or execution_date_fn can be passed to ExternalTaskSensor, but not both.

  • execution_date_fn (callable) – function that receives the current execution date and returns the desired execution dates to query. Either execution_delta or execution_date_fn can be passed to ExternalTaskSensor, but not both.

  • check_existence (bool) – Set to True to check if the external task exists (when external_task_id is not None) or check if the DAG to wait for exists (when external_task_id is None), and immediately cease waiting if the external task or DAG does not exist (default value: False).

template_fields = ['external_dag_id', 'external_task_id'][source]
ui_color = #19647e[source]
poke(self, context, session=None)[source]
_handle_execution_date_fn(self, context)[source]

This function is to handle backwards compatibility with how this operator was previously where it only passes the execution date, but also allow for the newer implementation to pass all context through as well, to allow for more sophisticated returns of dates to return. Namely, this function check the number of arguments in the execution_date_fn signature and if its 1, treat the legacy way, if it’s 2, pass the context as the 2nd argument, and if its more, throw an exception.

class airflow.sensors.external_task_sensor.ExternalTaskMarker(external_dag_id, external_task_id, execution_date='{{ execution_date.isoformat() }}', recursion_depth=10, *args, **kwargs)[source]

Bases: airflow.operators.dummy_operator.DummyOperator

Use this operator to indicate that a task on a different DAG depends on this task. When this task is cleared with “Recursive” selected, Airflow will clear the task on the other DAG and its downstream tasks recursively. Transitive dependencies are followed until the recursion_depth is reached.

Parameters

  • external_dag_id (str) – The dag_id that contains the dependent task that needs to be cleared.

  • external_task_id (str) – The task_id of the dependent task that needs to be cleared.

  • execution_date (str or datetime.datetime) – The execution_date of the dependent task that needs to be cleared.

  • recursion_depth – The maximum level of transitive dependencies allowed. Default is 10. This is mostly used for preventing cyclic dependencies. It is fine to increase this number if necessary. However, too many levels of transitive dependencies will make it slower to clear tasks in the web UI.

template_fields = ['external_dag_id', 'external_task_id', 'execution_date'][source]
ui_color = #19647e[source]

Was this entry helpful?