You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by po...@apache.org on 2021/12/05 23:04:08 UTC

[airflow] branch main updated: Add xcom clearing behaviour on task retries (#19968)

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 538612c  Add xcom clearing behaviour on task retries (#19968)
538612c is described below

commit 538612c3326b5fd0be4f4114f85e6f3063b5d49c
Author: Dmytro Kazanzhy <dk...@gmail.com>
AuthorDate: Mon Dec 6 01:03:38 2021 +0200

    Add xcom clearing behaviour on task retries (#19968)
    
    Co-authored-by: Dmytro Kazanzhy <dk...@demandbase.com>
---
 docs/apache-airflow/concepts/xcoms.rst | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/apache-airflow/concepts/xcoms.rst b/docs/apache-airflow/concepts/xcoms.rst
index 315c872..eb11ff7 100644
--- a/docs/apache-airflow/concepts/xcoms.rst
+++ b/docs/apache-airflow/concepts/xcoms.rst
@@ -38,6 +38,9 @@ You can also use XComs in :ref:`templates <concepts:jinja-templating>`::
 
 XComs are a relative of :doc:`variables`, with the main difference being that XComs are per-task-instance and designed for communication within a DAG run, while Variables are global and designed for overall configuration and value sharing.
 
+::
+
+  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
 ---------------