gene-bordegaray opened a new pull request, #23239:
URL: https://github.com/apache/datafusion/pull/23239
## Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
- Closes #23191.
- Related discussion: #23184, #23236.
## Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
Range partitioning can satisfy aggregate key partitioning: equal group keys
are already co-located, even though the partitioning is not hash-based.
This is the unary-operator step from the range partitioning discussion
before making broader public API changes around `HashPartitioned` /
`KeyPartitioned`.
## What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
- Let compatible range partitioning satisfy aggregate hash distribution
requirements in `EnforceDistribution`.
- Keep the behavior private to aggregate planning for now.
- Add sanity-check support and focused optimizer / SLT coverage.
## Are these changes tested?
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example, are
they covered by existing tests)?
-->
Yes:
- `cargo fmt --all -- --check`
- `cargo test -p datafusion --test core_integration range_aggregate --
--nocapture`
- `cargo test -p datafusion --test core_integration
range_grouping_set_aggregate_rehashes_with_grouping_id -- --nocapture`
## Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
Yes. Some range-partitioned aggregate plans can now avoid unnecessary hash
repartitioning.
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
