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

Posted to issues@calcite.apache.org by "Jinfeng Ni (JIRA)" <ji...@apache.org> on 2015/08/07 17:14:46 UTC

[jira] [Commented] (CALCITE-826) Use ProjectFactory in AggregateJoinTranposeRule and FilterJoinRule

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

Jinfeng Ni commented on CALCITE-826:
------------------------------------

Right, CALCITE-828 seems to be the right way to fix all similar problems like this one.  

> Use ProjectFactory in AggregateJoinTranposeRule and FilterJoinRule
> ------------------------------------------------------------------
>
>                 Key: CALCITE-826
>                 URL: https://issues.apache.org/jira/browse/CALCITE-826
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>             Fix For: 1.4.0-incubating
>
>
> RelOptUtil.pushDownJoinConditions is called in FilterJoinRule; it might create Project operators, but a ProjectFactory parameter is not provided. RelOptUtil.createProject that is called in AggregateJoinTranposeRule has the same issue.



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