You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Andrew Lamb (Jira)" <ji...@apache.org> on 2021/02/03 18:39:00 UTC
[jira] [Resolved] (ARROW-11431) [Rust] [DataFusion] Add support for
the SQL HAVING clause
[ https://issues.apache.org/jira/browse/ARROW-11431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Lamb resolved ARROW-11431.
---------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Issue resolved by pull request 9364
[https://github.com/apache/arrow/pull/9364]
> [Rust] [DataFusion] Add support for the SQL HAVING clause
> ---------------------------------------------------------
>
> Key: ARROW-11431
> URL: https://issues.apache.org/jira/browse/ARROW-11431
> Project: Apache Arrow
> Issue Type: New Feature
> Components: Rust - DataFusion
> Reporter: Daniel Russo
> Assignee: Daniel Russo
> Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> We do not yet have support for the SQL {{HAVING}} clause. {{HAVING}} is used to filter post-aggregation, typically against an aggregated column. For example:
> {code}
> SELECT c1, MAX(c2) FROM t GROUP BY c1 HAVING MAX(c2) > 100
> {code}
> {{HAVING}} expressions need not reference aggregates in the {{SELECT}}, for example:
> {code}
> SELECT c1, MAX(c2) FROM t GROUP BY c1 HAVING MIN(c2) > 100
> {code}
> {{HAVING}} expressions need not filter on aggregated columns, for example:
> {code}
> SELECT c1, MAX(c2) FROM t GROUP BY c1 HAVING c1 > 100
> {code}
> Lastly, {{HAVING}} expressions need not be used in conjunction with a {{GROUP BY}}, for example:
> {code}
> SELECT MAX(c1) FROM t HAVING MAX(c1) > 100
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)