You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "AlexRusuDatavid (via GitHub)" <gi...@apache.org> on 2025/09/01 10:10:49 UTC

[D] Pulling from xcom object storage [airflow]

GitHub user AlexRusuDatavid created a discussion: Pulling from xcom object storage

What is the intended way of pulling data from xcom object storage? 
`context[ti].xcom_pull` retrieves s3 refference in my case. 
The only way to actually get data is doing something like : 
`
actual_data = XCom.get_one(
    run_id=ti.run_id,
    task_id=task_id,
    dag_id=ti.dag_id,
    key=key
        )
`

GitHub link: https://github.com/apache/airflow/discussions/55132

----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org


Re: [D] Pulling from xcom object storage [airflow]

Posted by "AlexRusuDatavid (via GitHub)" <gi...@apache.org>.
GitHub user AlexRusuDatavid added a comment to the discussion: Pulling from xcom object storage

So when we xcom_push it actually uses our CustomObjectStorage serializer, but when pulling it uses basic postgres xcom? Isn't that kind of counter intuitive?

GitHub link: https://github.com/apache/airflow/discussions/55132#discussioncomment-14275282

----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org


Re: [D] Pulling from xcom object storage [airflow]

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
GitHub user potiuk added a comment to the discussion: Pulling from xcom object storage

Yep. That's the right way.

GitHub link: https://github.com/apache/airflow/discussions/55132#discussioncomment-14275214

----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org