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

Posted to issues@calcite.apache.org by "Luis Fernando Kauer (JIRA)" <ji...@apache.org> on 2017/11/08 12:23:00 UTC

[jira] [Created] (CALCITE-2044) Tweak cost of BindableTableScan to make sure Project is pushed through Aggregate

Luis Fernando Kauer created CALCITE-2044:
--------------------------------------------

             Summary: Tweak cost of BindableTableScan to make sure Project is pushed through Aggregate
                 Key: CALCITE-2044
                 URL: https://issues.apache.org/jira/browse/CALCITE-2044
             Project: Calcite
          Issue Type: Bug
          Components: core
            Reporter: Luis Fernando Kauer
            Assignee: Julian Hyde
            Priority: Minor


Similar to [CALCITE-1876].
Projects are not pushed to BindableTableScan when using ProjectableFilterableTable with aggregate functions.
The reason is that the cost of BindableTableScan does not use projects (and filters), so the planner chooses a plan with Project node removed by ProjectRemoveRule.
By tweaking the cost to use the number of used projects solved the problem.
Any suggestion on the cost formula to take both projects and filters into account?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)