You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Aman Sinha (JIRA)" <ji...@apache.org> on 2015/09/27 05:21:04 UTC

[jira] [Commented] (CALCITE-900) ProjectSetOpTransposeRule can be improved when the input is a SetOperator with Trivial Project on top

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

Aman Sinha commented on CALCITE-900:
------------------------------------

[~seanhychu] can you provide more details of the manifestation ?  I assume you mean that one could avoid unnecessary rule firings if such a trivial Project above the SetOp is not pushed below but rather left as-is and let the ProjectRemoveRule remove the project.   Sounds ok to me. The ProjectSetOpTransposeRule's matches() could check for trivial Project and return false. 

> ProjectSetOpTransposeRule can be improved when the input is a SetOperator with Trivial Project on top
> -----------------------------------------------------------------------------------------------------
>
>                 Key: CALCITE-900
>                 URL: https://issues.apache.org/jira/browse/CALCITE-900
>             Project: Calcite
>          Issue Type: Improvement
>          Components: core
>            Reporter: Sean Hsuan-Yi Chu
>            Assignee: Sean Hsuan-Yi Chu
>
> When SetOperator with Trivial Project on top, pushing this trivial project does not necessary. An improvement can be done if we just discard this trivial project. 



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