You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (Jira)" <ji...@apache.org> on 2022/12/08 20:56:00 UTC

[jira] [Commented] (CALCITE-5425) Should not pushdown filter through aggregate with an empty groupset

    [ https://issues.apache.org/jira/browse/CALCITE-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644987#comment-17644987 ] 

Julian Hyde commented on CALCITE-5425:
--------------------------------------

Agreed. {{AggregateProjectPullUpConstantsRule}} already has logic to deal with a similar case.

> Should not pushdown filter through aggregate with an empty groupset
> -------------------------------------------------------------------
>
>                 Key: CALCITE-5425
>                 URL: https://issues.apache.org/jira/browse/CALCITE-5425
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>            Reporter: Steve Carlin
>            Priority: Major
>
> If we are given a query 
> SELECT count(x) FROM tbl HAVING false;
> This query should produce an empty set.  
> We should not allow a filter to pass through this aggregate.  When the aggregate has no group by, there is always one implied group (for the whole dataset).  So if we apply the filter before the aggregate, the implied group will still be created.  This is not what we want, since the filter should produce an empty set.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)