dabla opened a new pull request, #48868:
URL: https://github.com/apache/airflow/pull/48868
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
Thank you for contributing! 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 committers for the review!
In case of an existing issue, reference it using one of the following:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
As I already explained at @potiuk and @ashb we are experimenting with
streamable/iterable XCom's which means Xcom's could be an iterable (now it' not
supported yet) which would be evaluated at runtime when the consumer operator
iterates over the results of the producing operator, which has the advantage of
having the producer operator not needing to fetch all pages before passing it
to the next operator, hence reducing memory usage as well as avoid unnecessary
waiting times, and thus leading to much higher throughput.
When doing such test, I discovered that due to that aspect, the XCom where
missing one important feature, which is filtering. We already have multiple
operations like map, zip and concat, which are very handy, but not a filter.
Not having this operation on the Xcom would mean I would again have to process
the full XCom iterable by applying the filtering through a PythonOperator,
which just removes the advantage of the streaming/iterable functionality before
being able to pass it to the consuming operator, hence why this PR.
This PR doesn't of course add the
[streaming](https://github.com/apache/airflow/pull/42572) functionality, as
this is still a WIP/POC, but at least would already provide us the filter
operation on an XCom which is missing today.
<!-- Please keep an empty line above the dashes. -->
---
**^ 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]
