dabla opened a new pull request, #68299:
URL: https://github.com/apache/airflow/pull/68299
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: [#ISSUE](https://github.com/apache/airflow/pull/68232)
-->
## Related PR's
Related to:
[#68214](https://github.com/apache/airflow/pull/68232)
[#60268](https://github.com/apache/airflow/pull/60268)
[#62922](https://github.com/apache/airflow/pull/62922)
## Why
Async `@task` functions currently cannot efficiently pull or push XCom
values because the existing `xcom_pull` and `xcom_push` implementations rely on
synchronous communication with the task supervisor. Invoking these methods from
an async task blocks the event loop, reducing the benefits of asynchronous
execution.
This change introduces asynchronous XCom operations, allowing async Python
tasks to interact with XComs without blocking the event loop.
This capability is also an important building block for the upcoming Task
Iteration feature (AIP-104). Task Iteration relies on the ability to persist
intermediate progress and results during execution, which requires non-blocking
XCom operations when used with async tasks. As such, this PR serves as
preparatory work for AIP-104 while also providing immediate value by enabling
fully asynchronous XCom interactions in existing async Python tasks.
In addition, this functionality lays the groundwork for future async
operators. As more operators adopt native async implementations, they will be
able to leverage asynchronous XCom operations without blocking the event loop,
enabling more efficient and scalable async execution patterns throughout
Airflow.
## How
- Add `axcom_pull`/`axcom_push` to `RuntimeTaskInstance`, awaiting the
supervisor round-trip via `asend` instead of blocking.
- Add `aget_one`/`aget_all`/`aset` to `BaseXCom` for async XCom retrieval
and storage.
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [ ] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
