[
https://issues.apache.org/jira/browse/CALCITE-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726465#comment-17726465
]
Julian Hyde commented on CALCITE-5425:
--------------------------------------
I see. Yes, I agree that you need a way to create a test case for
{{{}FilterAggregateTransposeRule{}}}, and using the {{create}} methods seems a
good way to prevent {{RelBuilder}} optimizing away the filter in your test.
> 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
> Assignee: Dan Zou
> 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)
