This is an automated email from the ASF dual-hosted git repository. ephraimanierobi pushed a commit to branch v2-6-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 1f64d3c42644efa649a606aa99daf39be1e3c2c1 Author: Wei Lee <[email protected]> AuthorDate: Mon Jun 26 22:19:57 2023 +0800 docs(authoring-and-scheduling/deferring): add a note that we'll need to restart triggerer to reflect any trigger change (#32140) (cherry picked from commit 51dbbaf40b90aa676cc706fd8c40c12cac66b9cc) --- 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 4755566670..b1e6c6be98 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
