[
https://issues.apache.org/jira/browse/AIRFLOW-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16828022#comment-16828022
]
jack commented on AIRFLOW-1832:
-------------------------------
There has been significant work for the xcom_push including unification done
in https://issues.apache.org/jira/browse/AIRFLOW-3249
Please check against newer airflow version and report back
> xcom_push is not reliable
> -------------------------
>
> Key: AIRFLOW-1832
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1832
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: Michelle Huang
> Priority: Major
>
> we have a few ETL jobs that are hitting a third party API, extracting data
> onto the Airflow server and then transforming and inserting that data into
> Redshift. we're using xcom_push in the extract function to store an
> identifier appended to the filename to be referenced in the transform
> function so we can grab the right file to transform. I'm noticing that
> xcom_push is not successfully pushing the value and xcom_pull is returning
> "None". this is happening across many of our scheduled jobs regularly and
> only just started happening on 11/16. manual triggers of the jobs run
> successfully to completion without issue. this only affects our scheduled
> runs and doesn't happen to all of them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
