Look at, the default is the same logical date as the current task or DAG.įor yesterday, use datetime.timedelta(days=1). Skipped_states ( Iterable | None) – Iterable of states to make this task mark as skipped, default is Noneįailed_states ( Iterable | None) – Iterable of failed or dis-allowed states, default is NoneĮxecution_delta ( datetime.timedelta | None) – time difference with the previous execution to EitherĮxternal_task_id or external_task_ids can be passed toĮxternal_task_group_id ( str | None) – The task_group_id that contains the task you want toĪllowed_states ( Iterable | None) – Iterable of allowed states, default is If None (default value) the sensor waits for the DAG. Using soft_fail = TrueĪs above will cause the sensor to skip if the target fails, but also if itĮxternal_dag_id ( str) – The dag_id that contains the task you want toĮxternal_task_id ( str | None) – The task_id that contains the task you want toĮxternal_task_ids ( Collection | None) – The list of task_ids that you want to wait for. Using skipped_states allows the sensor to skip if the targetįails, but still enter failed state on timeout. However, this is a contrivedĮxample-consider using skipped_states if you would like thisīehaviour. As a result, setting soft_fail=TrueĪnd failed_states= will result in the sensor If the external task enters a failed state and soft_fail = True the Note that soft_fail is respected when examining the failed_states. Get a sensor which goes green when the external task fails and immediately by setting allowed_states=Īnd failed_states= you will flip the behaviour to It is possible to alter the default behavior by setting states whichĬause the sensor to fail, e.g. If both happen together, then the failed state
Note that if you are monitoring multiple tasks, and one enters error stateĪnd the other enters a skipped state, then the external task will react to To change this, simply set skipped_states=. Without also having to clear the sensor).īy default, the ExternalTaskSensor will not skip if the external task skips. Until the sensor times out (thus giving you time to retry the external task Not fail if the external task fails, but will continue to check the status Succeed, at which point it will also succeed. Values for external_task_group_id and external_task_id can’t be set at the same time.īy default, the ExternalTaskSensor will wait for the external task to If both external_task_group_id and external_task_id are None (default), the sensor ExternalTaskSensor ( *, external_dag_id, external_task_id = None, external_task_ids = None, external_task_group_id = None, allowed_states = None, skipped_states = None, failed_states = None, execution_delta = None, execution_date_fn = None, check_existence = False, poll_interval = 2.0, deferrable = conf.getboolean('operators', 'default_deferrable', fallback=False), ** kwargs ) ¶īases: Ti_key – TaskInstance ID to return link for. Operator – The Airflow operator object this link is associated to. Note: The old signature of this function was (self, operator, dttm: datetime). name = 'External DAG' ¶ get_link ( operator, dttm ) ¶ It allows users to access DAG waited with ExternalTaskSensor or cleared by ExternalTaskMarker. Use this operator to indicate that a task on a different DAG depends on this task.Ĭlass _task. Waits for a different DAG, task group, or task to complete for a specific logical date. Operator link for ExternalTaskSensor and ExternalTaskMarker. What is not part of the Public Interface of Apache Airflow?.Using Public Interface to integrate with external services and applications.Using Public Interface to extend Airflow capabilities.ExternalTaskSensorLink._attrs_post_init_().ExternalTaskMarker.get_serialized_fields().ExternalTaskMarker.operator_extra_links.ExternalTaskSensor.get_external_task_group_task_ids().ExternalTaskSensor.operator_extra_links.Using the Public Interface for DAG Authors.
0 kommentar(er)
