Re: [PR] Clarify that XComModel is the default xcom backend [airflow]
amoghrajesh commented on PR #49390: URL: https://github.com/apache/airflow/pull/49390#issuecomment-2812869613 Closing as per review above -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] Clarify that XComModel is the default xcom backend [airflow]
amoghrajesh closed pull request #49390: Clarify that XComModel is the default xcom backend URL: https://github.com/apache/airflow/pull/49390 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] Clarify that XComModel is the default xcom backend [airflow]
amoghrajesh commented on code in PR #49390: URL: https://github.com/apache/airflow/pull/49390#discussion_r2048923189 ## 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 `. +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 `. Review Comment: Hmm yeah fair. Let me close this one./ -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] Clarify that XComModel is the default xcom backend [airflow]
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 `. +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 `. 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 `. +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 `. 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
[PR] Clarify that XComModel is the default xcom backend [airflow]
amoghrajesh opened a new pull request, #49390:
URL: https://github.com/apache/airflow/pull/49390
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information.
In case of fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party
License Policy](https://www.apache.org/legal/resolved.html#category-x).
In case of backwards incompatible changes please leave a note in a
newsfragment file, named `{pr_number}.significant.rst` or
`{issue_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
