You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "jin xing (Jira)" <ji...@apache.org> on 2019/08/21 04:42:00 UTC

[jira] [Assigned] (CALCITE-3274) Add FilterOnProjectToFilterUnifyRule for materialization matching

     [ https://issues.apache.org/jira/browse/CALCITE-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jin xing reassigned CALCITE-3274:
---------------------------------

    Assignee: jin xing

> Add FilterOnProjectToFilterUnifyRule for materialization matching
> -----------------------------------------------------------------
>
>                 Key: CALCITE-3274
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3274
>             Project: Calcite
>          Issue Type: Sub-task
>          Components: core
>            Reporter: jin xing
>            Assignee: jin xing
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> With current implementation of MV matching, below case fails
> {code:java}
>   @Test public void testFilterOnProject() {
>     String deduplicated =
>         "(select \"empid\", \"deptno\", \"name\", \"salary\", \"commission\"\n"
>             + "from \"emps\"\n"
>             + "group by \"empid\", \"deptno\", \"name\", \"salary\", \"commission\")";
>     String mv =
>         "select * from\n"
>             + "(select \"deptno\", sum(\"salary\") as \"sum_salary\", sum(\"commission\")\n"
>             + "from " + deduplicated + "\n"
>             + "group by \"deptno\")\n"
>             + "where \"sum_salary\" > 10";
>     String query =
>         "select * from\n"
>             + "(select \"deptno\", sum(\"salary\") as \"sum_salary\"\n"
>             + "from " + deduplicated + "\n"
>             + "group by \"deptno\")\n"
>             + "where \"sum_salary\" > 10";
>     checkMaterialize(mv, query);
>   }
> {code}
> {{Reason:}}
> After matching of the Aggregates, a compensating Project is added, but afterwards matching of filter fails to handle it.
> This issue proposes to handle such case where query and target are Filters and query has a compensating Project child node



--
This message was sent by Atlassian Jira
(v8.3.2#803003)