You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/04/15 11:29:00 UTC
[jira] [Updated] (CALCITE-7124) JdbcAggregateRule should push aggregate functions FILTER clauses to underlying SQL via JDBC adapter
[ https://issues.apache.org/jira/browse/CALCITE-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated CALCITE-7124:
------------------------------------
Labels: pull-request-available (was: )
> JdbcAggregateRule should push aggregate functions FILTER clauses to underlying SQL via JDBC adapter
> ---------------------------------------------------------------------------------------------------
>
> Key: CALCITE-7124
> URL: https://issues.apache.org/jira/browse/CALCITE-7124
> Project: Calcite
> Issue Type: Bug
> Reporter: xiong duan
> Priority: Major
> Labels: pull-request-available
>
> In SqlDialect, the supportsAggregateFunctionFilter function determine whether this dialect supports the use of FILTER clauses for aggregate functions.
> And In SqlImplementor, Calcite convert `SUM(x) FILTER(WHERE b) ==> SUM(CASE WHEN b THEN x END)` if the dialect does't support it.
> So In JdbcAggregateRule, we should push it down, then implement the same semantics using JdbcDialect.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)