Repository navigation
Conversation
2fc3b6b to
7176382
Compare
7176382 to
4678a09
Compare
|
Hello @fat-catTW - thank you for your contributions to Apache Airflow! The Airflow community has introduced a limit of 5 open pull requests at a time for contributors without write access to the repository. You currently have 17 open pull requests, so - as a one-time step of introducing the limit - we closed the ones where maintainers have not engaged yet:
These pull requests stay open because maintainers are already engaged in them - they count towards your limit:
This is not a judgement of you or of your changes. We never told contributors before that opening many pull requests at once was a problem, so there is nothing to feel bad about - and nothing is lost: your branches, commits and the review history stay where they are. What we ask you to do is to make your first prioritization decision: choose which of the pull requests above matter most to you, and reopen them (up to 5 open at a time, including the ones still open) with the "Reopen pull request" button or While your pull requests are waiting for review, the most valuable thing you can do is help in other ways - reviewing other contributors' pull requests, helping with issues, and taking part in the discussions on the devlist and Slack. Why we introduced the limit, what it means for you and how to reopen or restore a pull request is explained in https://github.com/apache/airflow/blob/main/contributing-docs/32_open_pull_request_limit.rst. Drafted-by: Claude Code (Opus 5); reviewed by @potiuk before posting |
Summary
This adds a batch XCom read path for mapped task input resolution.
When
DictOfListsExpandInput.resolve()sees multiple direct return-keyPlainXComArginputs that can be safely batched, it now fetches them through one grouped Execution API request instead of resolving eachXComArgone by one.The old resolution path is preserved as a fallback for cases that are not batched, including mapped upstreams, range map indexes, non-return keys, transformed/combined XComArgs, and custom XCom backends.
Changes
POST /execution/xcoms/batchfor fetching multiple XCom values for the same Dag run, key, and map index.BaseXCom.get_many()support for batch XCom fetches.expandinput.pyfor eligible directPlainXComArginputs.Tests
uv run ruff format ...uv run ruff check --fix ...git diff --checkprek run mypy-airflow-core --all-filesuv run --project scripts python scripts/ci/prek/check_execution_api_versions.pyuv run --project scripts python scripts/ci/prek/generate_supervisor_schemas_snapshot.pyuv run --project scripts python scripts/ci/prek/check_supervisor_schemas_versions.pyuv run --project task-sdk pytest task-sdk/tests/task_sdk/api/test_client.py::TestXCOMOperations task-sdk/tests/task_sdk/execution_time/test_supervisor.py::TestHandleRequest task-sdk/tests/task_sdk/definitions/test_mappedoperator.py::test_map_cross_product task-sdk/tests/task_sdk/definitions/test_mappedoperator.py::test_map_product_same -xvsuv run --project airflow-core pytest airflow-core/tests/unit/api_fastapi/execution_api/versions/v2025_04_28/test_xcom.py airflow-core/tests/unit/api_fastapi/execution_api/versions/v2026_10_30/test_xcoms.py -xvsWas generative AI tooling used to co-author this PR?
[X]Yes (please specify the tool below)Generated-by: [Codex] following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.