Lee-W opened a new pull request, #69309:
URL: https://github.com/apache/airflow/pull/69309
The `airflow.partition_mappers` package re-exports every mapper and window
except `FanOutMapper`, `WaitForAll`, and `MinimumCount` — even though the Task
SDK package already exports all three. This aligns the core exports with their
siblings and the SDK.
##### Why
- Core package root already exports all sibling mappers/windows — these
three were the only gap.
- Task SDK's matching package exports all three, so core was inconsistent
with it.
- For core-side plugin authors (custom mappers / wait policies running in
scheduler or Dag processor context), `ChainMapper` importing from the root
while `FanOutMapper` raises `ImportError` reads like a bug.
- Not a user-blocking issue — the deep-import path (e.g.
`airflow.partition_mappers.temporal.FanOutMapper`) always worked, and
serialization uses the full submodule path regardless.
##### What
- Add `FanOutMapper` (from `.temporal`), plus `MinimumCount` and
`WaitForAll` (from `.wait_policy`), to the package root imports and `__all__`.
- Add a test asserting all three are importable from the root and present in
`__all__`.
-
<!-- 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.
For user-facing UI changes, please attach before/after screenshots (or a
short
screen recording) so reviewers can assess the visual impact.
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
-->
---
##### 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]
