You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "assaf-grth (via GitHub)" <gi...@apache.org> on 2025/06/25 08:47:48 UTC

Re: [I] Raise KubernetesPodOperator do_xcom_push size limit [airflow]

assaf-grth commented on issue #15761:
URL: https://github.com/apache/airflow/issues/15761#issuecomment-3003947747

   Hi,
   Are there any updates on this subject?
   
   The [documentation](https://airflow.apache.org/docs/apache-airflow-providers-cncf-kubernetes/stable/operators.html#how-does-xcom-work) doesn't explicitly state that custom backends are supported when working with this operator, based on the different way it works
   
   [Here](https://airflow.apache.org/docs/apache-airflow/stable/best-practices.html#communication), Airflow recommends using xcom for smaller data sizes, and for larger ones, use path from external location where the ;large data would be stored
   
   Is this the practice to consider here?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org