From ce888dd86ae7308779aeeb243e64c9fc1cab031b Mon Sep 17 00:00:00 2001 From: Lewis John McGibbney Date: Thu, 6 Jan 2022 21:14:41 -0800 Subject: [PATCH 01/14] Augment XCom custom backend documentation --- docs/apache-airflow/concepts/xcoms.rst | 48 ++++++++++++++++++++++++++ 1 file changed, 48 insertions(+) diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst index eb11ff707fa5d..d57945285ec90 100644 --- a/docs/apache-airflow/concepts/xcoms.rst +++ b/docs/apache-airflow/concepts/xcoms.rst @@ -52,3 +52,51 @@ If you want to implement your own backend, you should subclass :class:`~airflow. There is also an ``orm_deserialize_value`` method that is called whenever the XCom objects are rendered for UI or reporting purposes; if you have large or expensive-to-retrieve values in your XComs, you should override this method to avoid calling that code (and instead return a lighter, incomplete representation) so the UI remains responsive. You can also override the ``clear`` method and use it when clearing results for given dags and tasks. This allows the custom XCom backend process the data lifecycle easier. + +Working with Custom Backends in Containers +------------------------------------------ + +Depending on where Airflow is deployed i.e., local, Docker, K8s, etc. it can be useful to be assured that a custom XCom backend is actually being initialized. For example, the complexity of the container environment can make it more difficult to determine if your backend is being loaded correctly during container deployment. Luckily the following guidance can be used to assist you in building confidence in your custom XCom implementation. + +Firstly, if you can exec into a terminal in the container then you should be able to do:: + + from airflow.models.xcom import XCom + print(XCom.__name__) + +which will print the actual class that is being used. + +Depending on how you've configured the backend, you can also examine airflow +configuration:: + + from airflow.settings import conf + conf.get("core", "xcom_backend") + +If using env vars check with ``env|grep AIRFLOW__CORE__XCOM``. + +Working with Custom Backends in K8s via Helm +-------------------------------------------- + +Running custom XCom backends in K8s can introduce even more complexity. Put simply, sometimes things go wrong which can be difficult to debug. + +For example, if you define a custom XCom backend in the Chart ``values.yaml`` (via the ``xcom_backend`` configuration) and Airflow fails to load the class, the entire Chart deployment will fail with each pod container attempting to restart time and time again. + +The problem is that it is very difficult to acquire logs from the container because there is a very small window of availability where the trace can be obtained. If you are fortunate enough to query the container logs at the right time, assuming that the custom backend value used is ``xcom_custom_backend.S3XComBackend``, you may see something similar to the following:: + + Traceback (most recent call last): + File "/home/airflow/.local/bin/airflow", line 8, in + sys.exit(main()) + File "/home/airflow/.local/lib/python3.9/site-packages/airflow/__main__.py", line 48, in main + args.func(args) + File "/home/airflow/.local/lib/python3.9/site-packages/airflow/cli/cli_parser.py", line 47, in command + ... + from airflow.models.xcom import XCOM_RETURN_KEY, XCom + File "/home/airflow/.local/lib/python3.9/site-packages/airflow/models/xcom.py", line 379, in + XCom = resolve_xcom_backend() + File "/home/airflow/.local/lib/python3.9/site-packages/airflow/models/xcom.py", line 369, in resolve_xcom_backend + clazz = conf.getimport("core", "xcom_backend", fallback=f"airflow.models.xcom.{BaseXCom.__name__}") + File "/home/airflow/.local/lib/python3.9/site-packages/airflow/configuration.py", line 485, in getimport + raise AirflowConfigException( + airflow.exceptions.AirflowConfigException: The object could not be loaded. Please check "xcom_backend" key in "core" section. Current value: "xcom_custom_backend.S3XComBackend". + [2022-01-06 00:02:16,880] {settings.py:331} DEBUG - Disposing DB connection pool (PID 214) + +As you can see, in this example the path to the custom XCom is incorrect. This in turn prevents the entire Helm chart from deploying successfully. \ No newline at end of file From 28c2a30ce812db3fdd8627618225f99a6701e97a Mon Sep 17 00:00:00 2001 From: Lewis John McGibbney Date: Fri, 7 Jan 2022 10:51:51 -0800 Subject: [PATCH 02/14] Augment XCom custom backend documentation --- docs/apache-airflow/concepts/xcoms.rst | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst index d57945285ec90..58a2698ea0681 100644 --- a/docs/apache-airflow/concepts/xcoms.rst +++ b/docs/apache-airflow/concepts/xcoms.rst @@ -42,8 +42,8 @@ XComs are a relative of :doc:`variables`, with the main difference being that XC Note: If the first task run is not succeeded then on every retry task XComs will be cleared to make the task run idempotent. -Custom Backends ---------------- +Custom XCom Backends +-------------------- The XCom system has interchangeable backends, and you can set which backend is being used via the ``xcom_backend`` configuration option. @@ -51,10 +51,10 @@ If you want to implement your own backend, you should subclass :class:`~airflow. There is also an ``orm_deserialize_value`` method that is called whenever the XCom objects are rendered for UI or reporting purposes; if you have large or expensive-to-retrieve values in your XComs, you should override this method to avoid calling that code (and instead return a lighter, incomplete representation) so the UI remains responsive. -You can also override the ``clear`` method and use it when clearing results for given dags and tasks. This allows the custom XCom backend process the data lifecycle easier. +You can also override the ``clear`` method and use it when clearing results for given dags and tasks. This allows the custom XCom backend to process the data lifecycle easier. -Working with Custom Backends in Containers ------------------------------------------- +Working with Custom XCom Backends in Containers +----------------------------------------------- Depending on where Airflow is deployed i.e., local, Docker, K8s, etc. it can be useful to be assured that a custom XCom backend is actually being initialized. For example, the complexity of the container environment can make it more difficult to determine if your backend is being loaded correctly during container deployment. Luckily the following guidance can be used to assist you in building confidence in your custom XCom implementation. @@ -76,11 +76,13 @@ If using env vars check with ``env|grep AIRFLOW__CORE__XCOM``. Working with Custom Backends in K8s via Helm -------------------------------------------- -Running custom XCom backends in K8s can introduce even more complexity. Put simply, sometimes things go wrong which can be difficult to debug. +Running custom XCom backends in K8s will introduce even more complexity to you Airflow deployment. Put simply, sometimes things go wrong which can be difficult to debug. For example, if you define a custom XCom backend in the Chart ``values.yaml`` (via the ``xcom_backend`` configuration) and Airflow fails to load the class, the entire Chart deployment will fail with each pod container attempting to restart time and time again. -The problem is that it is very difficult to acquire logs from the container because there is a very small window of availability where the trace can be obtained. If you are fortunate enough to query the container logs at the right time, assuming that the custom backend value used is ``xcom_custom_backend.S3XComBackend``, you may see something similar to the following:: +When deploying in K8s your custom XCom backend needs to be reside in a ``config`` directory otherwise it cannot be located during Chart deployment. + +An observed problem is that it is very difficult to acquire logs from the container because there is a very small window of availability where the trace can be obtained. If you are fortunate enough to query the container logs at the right time, assuming that the custom backend value used is ``xcom_custom_backend.S3XComBackend``, you may see something similar to the following:: Traceback (most recent call last): File "/home/airflow/.local/bin/airflow", line 8, in From 40137bb7af72f09b86572be4f74d8559354430bc Mon Sep 17 00:00:00 2001 From: Lewis John McGibbney Date: Fri, 7 Jan 2022 15:03:21 -0800 Subject: [PATCH 03/14] Augment XCom custom backend documentation --- docs/apache-airflow/concepts/xcoms.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst index 58a2698ea0681..26401c764a5ea 100644 --- a/docs/apache-airflow/concepts/xcoms.rst +++ b/docs/apache-airflow/concepts/xcoms.rst @@ -101,4 +101,4 @@ An observed problem is that it is very difficult to acquire logs from the contai airflow.exceptions.AirflowConfigException: The object could not be loaded. Please check "xcom_backend" key in "core" section. Current value: "xcom_custom_backend.S3XComBackend". [2022-01-06 00:02:16,880] {settings.py:331} DEBUG - Disposing DB connection pool (PID 214) -As you can see, in this example the path to the custom XCom is incorrect. This in turn prevents the entire Helm chart from deploying successfully. \ No newline at end of file +As you can see, in this example the path to the custom XCom is incorrect. This in turn prevents the entire Helm chart from deploying successfully. From 60f08aad432ef1765d2073679a5693385e1204a7 Mon Sep 17 00:00:00 2001 From: Lewis John McGibbney Date: Fri, 7 Jan 2022 20:13:19 -0800 Subject: [PATCH 04/14] Augment XCom custom backend documentation --- docs/apache-airflow/concepts/xcoms.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst index 26401c764a5ea..62adc7c185cd7 100644 --- a/docs/apache-airflow/concepts/xcoms.rst +++ b/docs/apache-airflow/concepts/xcoms.rst @@ -60,6 +60,8 @@ Depending on where Airflow is deployed i.e., local, Docker, K8s, etc. it can be Firstly, if you can exec into a terminal in the container then you should be able to do:: +.. code-block:: python + from airflow.models.xcom import XCom print(XCom.__name__) @@ -68,6 +70,8 @@ which will print the actual class that is being used. Depending on how you've configured the backend, you can also examine airflow configuration:: +.. code-block:: python + from airflow.settings import conf conf.get("core", "xcom_backend") @@ -84,6 +88,8 @@ When deploying in K8s your custom XCom backend needs to be reside in a ``config` An observed problem is that it is very difficult to acquire logs from the container because there is a very small window of availability where the trace can be obtained. If you are fortunate enough to query the container logs at the right time, assuming that the custom backend value used is ``xcom_custom_backend.S3XComBackend``, you may see something similar to the following:: +.. code-block:: python + Traceback (most recent call last): File "/home/airflow/.local/bin/airflow", line 8, in sys.exit(main()) From 4230e500441a5b169e1c1835c101b55abe6037b7 Mon Sep 17 00:00:00 2001 From: Lewis John McGibbney Date: Mon, 10 Jan 2022 16:14:38 -0800 Subject: [PATCH 05/14] Augment xcom docs --- docs/apache-airflow/concepts/xcoms.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst index 62adc7c185cd7..33b1a376ff9e2 100644 --- a/docs/apache-airflow/concepts/xcoms.rst +++ b/docs/apache-airflow/concepts/xcoms.rst @@ -88,7 +88,7 @@ When deploying in K8s your custom XCom backend needs to be reside in a ``config` An observed problem is that it is very difficult to acquire logs from the container because there is a very small window of availability where the trace can be obtained. If you are fortunate enough to query the container logs at the right time, assuming that the custom backend value used is ``xcom_custom_backend.S3XComBackend``, you may see something similar to the following:: -.. code-block:: python +:: Traceback (most recent call last): File "/home/airflow/.local/bin/airflow", line 8, in From 2c637d5f97f0672aabe2f0142d4b9d1936850543 Mon Sep 17 00:00:00 2001 From: Lewis John McGibbney Date: Sat, 22 Jan 2022 17:11:10 -0800 Subject: [PATCH 06/14] Augment xcom docs --- docs/apache-airflow/concepts/xcoms.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst index 33b1a376ff9e2..f114afac9cc49 100644 --- a/docs/apache-airflow/concepts/xcoms.rst +++ b/docs/apache-airflow/concepts/xcoms.rst @@ -62,7 +62,8 @@ Firstly, if you can exec into a terminal in the container then you should be abl .. code-block:: python - from airflow.models.xcom import XCom + from airflow.models.xcom import XCom + print(XCom.__name__) which will print the actual class that is being used. @@ -73,6 +74,7 @@ configuration:: .. code-block:: python from airflow.settings import conf + conf.get("core", "xcom_backend") If using env vars check with ``env|grep AIRFLOW__CORE__XCOM``. From 37b895814fc0604f15263e7a588628acb069b829 Mon Sep 17 00:00:00 2001 From: Lewis John McGibbney Date: Sat, 22 Jan 2022 17:55:02 -0800 Subject: [PATCH 07/14] Augment xcom docs --- docs/apache-airflow/concepts/xcoms.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst index f114afac9cc49..2c2ce1e6531e7 100644 --- a/docs/apache-airflow/concepts/xcoms.rst +++ b/docs/apache-airflow/concepts/xcoms.rst @@ -63,7 +63,7 @@ Firstly, if you can exec into a terminal in the container then you should be abl .. code-block:: python from airflow.models.xcom import XCom - + print(XCom.__name__) which will print the actual class that is being used. @@ -74,7 +74,7 @@ configuration:: .. code-block:: python from airflow.settings import conf - + conf.get("core", "xcom_backend") If using env vars check with ``env|grep AIRFLOW__CORE__XCOM``. @@ -98,7 +98,6 @@ An observed problem is that it is very difficult to acquire logs from the contai File "/home/airflow/.local/lib/python3.9/site-packages/airflow/__main__.py", line 48, in main args.func(args) File "/home/airflow/.local/lib/python3.9/site-packages/airflow/cli/cli_parser.py", line 47, in command - ... from airflow.models.xcom import XCOM_RETURN_KEY, XCom File "/home/airflow/.local/lib/python3.9/site-packages/airflow/models/xcom.py", line 379, in XCom = resolve_xcom_backend() @@ -108,5 +107,6 @@ An observed problem is that it is very difficult to acquire logs from the contai raise AirflowConfigException( airflow.exceptions.AirflowConfigException: The object could not be loaded. Please check "xcom_backend" key in "core" section. Current value: "xcom_custom_backend.S3XComBackend". [2022-01-06 00:02:16,880] {settings.py:331} DEBUG - Disposing DB connection pool (PID 214) + As you can see, in this example the path to the custom XCom is incorrect. This in turn prevents the entire Helm chart from deploying successfully. From d6d12e6169f92bfe6114857523d4014a071f8086 Mon Sep 17 00:00:00 2001 From: Lewis John McGibbney Date: Thu, 27 Jan 2022 08:49:02 -0800 Subject: [PATCH 08/14] Augment xcom docs --- docs/apache-airflow/concepts/xcoms.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst index 2c2ce1e6531e7..415c7ff342afd 100644 --- a/docs/apache-airflow/concepts/xcoms.rst +++ b/docs/apache-airflow/concepts/xcoms.rst @@ -62,7 +62,7 @@ Firstly, if you can exec into a terminal in the container then you should be abl .. code-block:: python - from airflow.models.xcom import XCom + from airflow.models.xcom import XCom print(XCom.__name__) @@ -107,6 +107,6 @@ An observed problem is that it is very difficult to acquire logs from the contai raise AirflowConfigException( airflow.exceptions.AirflowConfigException: The object could not be loaded. Please check "xcom_backend" key in "core" section. Current value: "xcom_custom_backend.S3XComBackend". [2022-01-06 00:02:16,880] {settings.py:331} DEBUG - Disposing DB connection pool (PID 214) - + As you can see, in this example the path to the custom XCom is incorrect. This in turn prevents the entire Helm chart from deploying successfully. From 328f45035713c3a68fbdbcf459eae8cd2bf1d48a Mon Sep 17 00:00:00 2001 From: Lewis John McGibbney Date: Thu, 27 Jan 2022 13:27:41 -0800 Subject: [PATCH 09/14] Augment xcom docs --- docs/apache-airflow/concepts/xcoms.rst | 23 +---------------------- 1 file changed, 1 insertion(+), 22 deletions(-) diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst index 415c7ff342afd..5a737c0d68c98 100644 --- a/docs/apache-airflow/concepts/xcoms.rst +++ b/docs/apache-airflow/concepts/xcoms.rst @@ -88,25 +88,4 @@ For example, if you define a custom XCom backend in the Chart ``values.yaml`` (v When deploying in K8s your custom XCom backend needs to be reside in a ``config`` directory otherwise it cannot be located during Chart deployment. -An observed problem is that it is very difficult to acquire logs from the container because there is a very small window of availability where the trace can be obtained. If you are fortunate enough to query the container logs at the right time, assuming that the custom backend value used is ``xcom_custom_backend.S3XComBackend``, you may see something similar to the following:: - -:: - - Traceback (most recent call last): - File "/home/airflow/.local/bin/airflow", line 8, in - sys.exit(main()) - File "/home/airflow/.local/lib/python3.9/site-packages/airflow/__main__.py", line 48, in main - args.func(args) - File "/home/airflow/.local/lib/python3.9/site-packages/airflow/cli/cli_parser.py", line 47, in command - from airflow.models.xcom import XCOM_RETURN_KEY, XCom - File "/home/airflow/.local/lib/python3.9/site-packages/airflow/models/xcom.py", line 379, in - XCom = resolve_xcom_backend() - File "/home/airflow/.local/lib/python3.9/site-packages/airflow/models/xcom.py", line 369, in resolve_xcom_backend - clazz = conf.getimport("core", "xcom_backend", fallback=f"airflow.models.xcom.{BaseXCom.__name__}") - File "/home/airflow/.local/lib/python3.9/site-packages/airflow/configuration.py", line 485, in getimport - raise AirflowConfigException( - airflow.exceptions.AirflowConfigException: The object could not be loaded. Please check "xcom_backend" key in "core" section. Current value: "xcom_custom_backend.S3XComBackend". - [2022-01-06 00:02:16,880] {settings.py:331} DEBUG - Disposing DB connection pool (PID 214) - - -As you can see, in this example the path to the custom XCom is incorrect. This in turn prevents the entire Helm chart from deploying successfully. +An observed problem is that it is very difficult to acquire logs from the container because there is a very small window of availability where the trace can be obtained. The only way you can determine the root cause is if you are fortunate enough to query and acquire the container logs at the right time. This in turn prevents the entire Helm chart from deploying successfully. From 2f13ed96b40450275a854a5a2442c6d55e12e3c1 Mon Sep 17 00:00:00 2001 From: Lewis John McGibbney Date: Wed, 2 Feb 2022 09:26:30 -0800 Subject: [PATCH 10/14] Update docs/apache-airflow/concepts/xcoms.rst Co-authored-by: Tzu-ping Chung --- docs/apache-airflow/concepts/xcoms.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst index 5a737c0d68c98..ba2d9b58fe71b 100644 --- a/docs/apache-airflow/concepts/xcoms.rst +++ b/docs/apache-airflow/concepts/xcoms.rst @@ -77,7 +77,7 @@ configuration:: conf.get("core", "xcom_backend") -If using env vars check with ``env|grep AIRFLOW__CORE__XCOM``. +If using env vars, check with ``env|grep AIRFLOW__CORE__XCOM``. Working with Custom Backends in K8s via Helm -------------------------------------------- From 59028b571c87d889eec7d15dc97a250a25899e55 Mon Sep 17 00:00:00 2001 From: Lewis John McGibbney Date: Wed, 2 Feb 2022 09:26:54 -0800 Subject: [PATCH 11/14] Update docs/apache-airflow/concepts/xcoms.rst Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> --- docs/apache-airflow/concepts/xcoms.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst index ba2d9b58fe71b..88d7e8e575f21 100644 --- a/docs/apache-airflow/concepts/xcoms.rst +++ b/docs/apache-airflow/concepts/xcoms.rst @@ -88,4 +88,4 @@ For example, if you define a custom XCom backend in the Chart ``values.yaml`` (v When deploying in K8s your custom XCom backend needs to be reside in a ``config`` directory otherwise it cannot be located during Chart deployment. -An observed problem is that it is very difficult to acquire logs from the container because there is a very small window of availability where the trace can be obtained. The only way you can determine the root cause is if you are fortunate enough to query and acquire the container logs at the right time. This in turn prevents the entire Helm chart from deploying successfully. +An observed problem is that it is very difficult to acquire logs from the container because there is a very small window of availability where the trace can be obtained. The only way you can determine the root cause is if you are fortunate enough to query and acquire the container logs at the right time. This in turn prevents the entire Helm chart from deploying successfully. From ec019363bc976e05a4660be6c8e7350cd96592b5 Mon Sep 17 00:00:00 2001 From: Lewis John McGibbney Date: Wed, 2 Feb 2022 17:42:25 -0800 Subject: [PATCH 12/14] Update docs/apache-airflow/concepts/xcoms.rst Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> --- docs/apache-airflow/concepts/xcoms.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst index 88d7e8e575f21..12681dd58a0c6 100644 --- a/docs/apache-airflow/concepts/xcoms.rst +++ b/docs/apache-airflow/concepts/xcoms.rst @@ -58,7 +58,7 @@ Working with Custom XCom Backends in Containers Depending on where Airflow is deployed i.e., local, Docker, K8s, etc. it can be useful to be assured that a custom XCom backend is actually being initialized. For example, the complexity of the container environment can make it more difficult to determine if your backend is being loaded correctly during container deployment. Luckily the following guidance can be used to assist you in building confidence in your custom XCom implementation. -Firstly, if you can exec into a terminal in the container then you should be able to do:: +Firstly, if you can exec into a terminal in the container then you should be able to do: .. code-block:: python From 0bc737f00e760220f262a4e41da70b7609bb1714 Mon Sep 17 00:00:00 2001 From: Lewis John McGibbney Date: Wed, 2 Feb 2022 18:20:27 -0800 Subject: [PATCH 13/14] Update docs/apache-airflow/concepts/xcoms.rst Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> --- docs/apache-airflow/concepts/xcoms.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst index 12681dd58a0c6..9d883b8bfe474 100644 --- a/docs/apache-airflow/concepts/xcoms.rst +++ b/docs/apache-airflow/concepts/xcoms.rst @@ -68,8 +68,7 @@ Firstly, if you can exec into a terminal in the container then you should be abl which will print the actual class that is being used. -Depending on how you've configured the backend, you can also examine airflow -configuration:: +You can also examine Airflow's configuration: .. code-block:: python From 053d12b6b7fd752b766956194a2f1808bf53a8f8 Mon Sep 17 00:00:00 2001 From: Lewis John McGibbney Date: Wed, 2 Feb 2022 18:20:38 -0800 Subject: [PATCH 14/14] Update docs/apache-airflow/concepts/xcoms.rst Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> --- docs/apache-airflow/concepts/xcoms.rst | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst index 9d883b8bfe474..57b9e54477fb6 100644 --- a/docs/apache-airflow/concepts/xcoms.rst +++ b/docs/apache-airflow/concepts/xcoms.rst @@ -76,8 +76,6 @@ You can also examine Airflow's configuration: conf.get("core", "xcom_backend") -If using env vars, check with ``env|grep AIRFLOW__CORE__XCOM``. - Working with Custom Backends in K8s via Helm --------------------------------------------