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 2017/11/15 20:08:01 UTC

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

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

Julian Hyde resolved CALCITE-2044.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.15.0

Fixed in [a8505d2b|http://git-wip-us.apache.org/repos/asf/calcite/commit/a8505d2b]. Thanks for the PR, [~lfkauer]!

> 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
>             Fix For: 1.15.0
>
>
> 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)