From 8c4c1e42bdc00e2e72fe0ddee6a5a2c441aa0382 Mon Sep 17 00:00:00 2001 From: Wei Lee Date: Mon, 26 Jun 2023 18:20:24 +0800 Subject: [PATCH] docs(authoring-and-scheduling/deferring): add a note that we'll need to restart triggerer to reflect any trigger change --- docs/apache-airflow/authoring-and-scheduling/deferring.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/apache-airflow/authoring-and-scheduling/deferring.rst b/docs/apache-airflow/authoring-and-scheduling/deferring.rst index 4755566670066..b1e6c6be983d0 100644 --- a/docs/apache-airflow/authoring-and-scheduling/deferring.rst +++ b/docs/apache-airflow/authoring-and-scheduling/deferring.rst @@ -55,6 +55,7 @@ Writing a deferrable operator takes a bit more work. There are some main points * Your Operator will be stopped and removed from its worker while deferred, and no state will persist automatically. You can persist state by asking Airflow to resume you at a certain method or pass certain kwargs, but that's it. * You can defer multiple times, and you can defer before/after your Operator does significant work, or only defer if certain conditions are met (e.g. a system does not have an immediate answer). Deferral is entirely under your control. * Any Operator can defer; no special marking on its class is needed, and it's not limited to Sensors. +* In order for any changes to a Trigger to be reflected, the *triggerer* needs to be restarted whenever the Trigger is modified. Triggering Deferral