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

["Ash Berlin-Taylor (Jira)" <ji...@apache.org>]

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

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

Nothing should be caching it. What/how do you set {{running_cluster}}

If you look at the Task Instance Detail view, you should see job_flow_id with your {{ti.xcom_pull}} template, and if you switch over to the rendered tab it should show the right value.

Have you checked if the right value from "initialization_emr_cluster" is getting put in to the xcom? (If the value looks a bit "mangled" in the UI don't worry about that, it's a visual bug where we haven't unpickled the value before display on that view)



> 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)