airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Song Liu <>
Subject 答复: About the difference between xcom and variable
Date Thu, 10 May 2018 08:55:07 GMT
It seems that variable doesn't remove the duplication if have.

Anyway XCom.get / XCom.set looks like more flexible and it meets the requirement.

发件人: Song Liu <>
发送时间: 2018年5月9日 7:22
主题: About the difference between xcom and variable


For the cross-task communication, there are two options:
- xcom
- variable

if I have make sure the key of variable is global unique (such uuid), is there any other limitations
or cons for using variable instead of xcom ? since that xcom should specify the task_id which
is used not very convenient compared with variable.

Any information is appreciated.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message