You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (Jira)" <ji...@apache.org> on 2019/08/23 15:27:00 UTC

[jira] [Commented] (AIRFLOW-5295) DAG doesn't take the last value of XCOM

    [ https://issues.apache.org/jira/browse/AIRFLOW-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914348#comment-16914348 ] 

Ash Berlin-Taylor commented on AIRFLOW-5295:
--------------------------------------------

This is odd. There is nothing in the code that I can think of that would cache the XCom values.

Can you show where/how in your task you get the XCOM value?

> DAG doesn't take the last value of XCOM
> ---------------------------------------
>
>                 Key: AIRFLOW-5295
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5295
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: DAG
>    Affects Versions: 1.8.0, 1.10.3
>            Reporter: Pierrick Boitel
>            Priority: Minor
>
> I have sometimes failure on my DAG and need to re-run some tasks. Some of these emits a new value for a XCOM, but when following tasks runs, they generally takes the old value for this XCOM (although the value is good in Airflow's database). In order to have the good value, I have to clear my tasks several time (more than 10 time sometimes) which is really painfull.
> I suppose that the DAG on the scheduler keeps the value on cache but not sure on this. I didn't enable pickking for the JSON too.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)