Skip to content

Conversation

@amoghrajesh
Copy link
Contributor

  • MAX_XCOM_SIZE is a hardcoded implementation detail and is not really part of any API contract.
  • The value is not configurable and is unlikely to change at any point of time.

Only the google and amazon transfers were importing it. I have hardcoded it in there.
Let me know if this needs a newsfragment.


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
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.

@amoghrajesh amoghrajesh requested a review from kaxil July 7, 2025 13:53
@boring-cyborg boring-cyborg bot added area:providers provider:amazon AWS/Amazon - related issues provider:google Google (including GCP) related issues labels Jul 7, 2025
@amoghrajesh amoghrajesh changed the title Remove MAX_XCOM_SIZE constant from Airflow core Remove MAX_XCOM_SIZE hardcoded constant from Airflow core Jul 7, 2025
@amoghrajesh amoghrajesh added this to the Airflow 3.1.0 milestone Jul 7, 2025
@amoghrajesh amoghrajesh merged commit 5fe1220 into apache:main Jul 7, 2025
79 checks passed
@amoghrajesh amoghrajesh deleted the remove-max_xcom branch July 7, 2025 15:36
HsiuChuanHsu pushed a commit to HsiuChuanHsu/airflow that referenced this pull request Jul 10, 2025
stephen-bracken pushed a commit to stephen-bracken/airflow that referenced this pull request Jul 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:providers provider:amazon AWS/Amazon - related issues provider:google Google (including GCP) related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants