[jira] [Commented] (CALCITE-675) Add planner rule that removes simple Project beneath Aggregate

["Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org>]

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

Jesus Camacho Rodriguez commented on CALCITE-675:
-------------------------------------------------

[~julianhyde], isn't this what {{AggregateProjectMergeRule}} do? Or you have something else in mind?

> Add planner rule that removes simple Project beneath Aggregate
> --------------------------------------------------------------
>
>                 Key: CALCITE-675
>                 URL: https://issues.apache.org/jira/browse/CALCITE-675
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>
> If you have a simple Project that just re-orders or renames fields, or projects a subset, and it is directly beneath an Aggregate, then the Aggregate can be rewritten in terms of the Project's input.
> This rule should also apply if the project computes expressions, if those expressions are not used.
> This rule will help AggegateJoinTransposeRule apply in more cases. For example, it cannot currently apply to {code}select distinct dept.deptno from emp join dept using (deptno){code} because the join projects 2 columns and the aggregate only uses one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)