This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new bbb03a7c17 Update deferring.rst (#38122)
bbb03a7c17 is described below
commit bbb03a7c172aa4d688f6e126d399240f817b315f
Author: 9uzman <[email protected]>
AuthorDate: Fri Mar 15 12:52:20 2024 -0300
Update deferring.rst (#38122)
---
docs/apache-airflow/authoring-and-scheduling/deferring.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/apache-airflow/authoring-and-scheduling/deferring.rst
b/docs/apache-airflow/authoring-and-scheduling/deferring.rst
index 912e60dbca..218eb04a36 100644
--- a/docs/apache-airflow/authoring-and-scheduling/deferring.rst
+++ b/docs/apache-airflow/authoring-and-scheduling/deferring.rst
@@ -109,7 +109,7 @@ If you want to trigger deferral, at any place in your
operator, you can call ``s
When you opt to defer, your operator will stop executing at that point and be
removed from its current worker. No state will persist, such as local variables
or attributes set on ``self``. When your operator resumes, it resumes as a new
instance of it. The only way you can pass state from the old instance of the
operator to the new one is with ``method_name`` and ``kwargs``.
-When your operator resumes, Airflow adds an ``event`` object to the kwargs
passed to the ``method_name`` method. This ``event`` object contains the
payload from the trigger event that resumed your operator. Depending on the
trigger, this can be useful to your operator, like it's a status code or URL to
fetch results. Or, it might be unimportant information, like a datetime. Your
``method_name`` method, however, *must* accept ``event`` as a keyword argument.
+When your operator resumes, Airflow adds a ``context`` object and an ``event``
object to the kwargs passed to the ``method_name`` method. This ``event``
object contains the payload from the trigger event that resumed your operator.
Depending on the trigger, this can be useful to your operator, like it's a
status code or URL to fetch results. Or, it might be unimportant information,
like a datetime. Your ``method_name`` method, however, *must* accept
``context`` and ``event`` as a keyword [...]
If your operator returns from either its first ``execute()`` method when it's
new, or a subsequent method specified by ``method_name``, it will be considered
complete and finish executing.
