yjshen opened a new pull request, #5868:
URL: https://github.com/apache/arrow-datafusion/pull/5868
# 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 #.
# 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.
-->
This pull request introduces support for the FILTER (WHERE) clause in
aggregate expressions. This feature enables users to filter the rows that are
considered for aggregation, similar to how it is done in popular SQL databases
such as PostgreSQL, SQLite, Spark, and Hive.
# What changes are included in this PR?
1. The `physical_plan/aggregate` module is where the majority of the work
for this project was completed.
2. Additionally, there were changes made to the mechanism that routes the
optional filter through the optimizer and execution code path.
<!--
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.
-->
# Are these changes tested?
New tests were added in `group_by.rs` to cover various scenarios using the
FILTER (WHERE) clause with different situations.
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
4. 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)?
-->
# Are there any user-facing changes?
Yes, users can now use the FILTER (WHERE) clause in aggregate expressions in
their SQL queries, providing more flexibility and control over the aggregation.
This change is backward compatible, and existing queries without the FILTER
(WHERE) clause should continue to work as expected.
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!--
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]
