[
https://issues.apache.org/jira/browse/CALCITE-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16252077#comment-16252077
]
Julian Hyde commented on CALCITE-2044:
--------------------------------------
{{RelDataTypeFactory.builder()}} isn't actually deprecated. It just has the
annotation {{@SuppressWarnings("deprecation")}} to stop the compiler
complaining that we are using {{FieldInfoBuilder}}, which was deprecated as of
CALCITE-1929. I wanted to change the return type to
{{RelDataTypeFactory.Builder}}, which is {{FieldInfoBuilder}}'s base class and
is not deprecated, but I could not do so due to binary compatibility.
So yes, use {{RelDataTypeFactory.builder()}}. I will make that change for you.
> 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)
