kaxil commented on code in PR #49390: URL: https://github.com/apache/airflow/pull/49390#discussion_r2048795807
########## airflow-core/docs/core-concepts/xcoms.rst: ########## @@ -83,7 +83,7 @@ An example of pushing multiple XComs and pulling them individually: Object Storage XCom Backend --------------------------- -The default XCom backend, BaseXCom, stores XComs in the Airflow database, which works well for small values but can cause issues with large values or a high volume of XComs. To overcome this limitation, object storage is recommended for efficiently handling larger data. For a detailed overview, refer to the :doc:`documentation <apache-airflow-providers-common-io:xcom_backend>`. +The default XCom backend, XComModel, stores XComs in the Airflow database, which works well for small values but can cause issues with large values or a high volume of XComs. To overcome this limitation, object storage is recommended for efficiently handling larger data. For a detailed overview, refer to the :doc:`documentation <apache-airflow-providers-common-io:xcom_backend>`. Review Comment: I don't think it matter since `BaseXCom` also stores thing in DB via API server ########## airflow-core/docs/core-concepts/xcoms.rst: ########## @@ -83,7 +83,7 @@ An example of pushing multiple XComs and pulling them individually: Object Storage XCom Backend --------------------------- -The default XCom backend, BaseXCom, stores XComs in the Airflow database, which works well for small values but can cause issues with large values or a high volume of XComs. To overcome this limitation, object storage is recommended for efficiently handling larger data. For a detailed overview, refer to the :doc:`documentation <apache-airflow-providers-common-io:xcom_backend>`. +The default XCom backend, XComModel, stores XComs in the Airflow database, which works well for small values but can cause issues with large values or a high volume of XComs. To overcome this limitation, object storage is recommended for efficiently handling larger data. For a detailed overview, refer to the :doc:`documentation <apache-airflow-providers-common-io:xcom_backend>`. Review Comment: I don't think it matters since `BaseXCom` also stores thing in DB via API server -- 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-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
