You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2015/08/20 12:14:46 UTC
[jira] [Commented] (CALCITE-850) Remove push down expressions from
FilterJoinRule and create a new rule for it
[ https://issues.apache.org/jira/browse/CALCITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14704632#comment-14704632 ]
Jesus Camacho Rodriguez commented on CALCITE-850:
-------------------------------------------------
I have created a pull request in https://github.com/apache/incubator-calcite/pull/122 . Changes in plans are swapping of join inputs.
[~julianhyde], [~jni], [~vladimirsitnikov], you all seemed to be involved in CALCITE-457, any thoughts? Thanks
> Remove push down expressions from FilterJoinRule and create a new rule for it
> -----------------------------------------------------------------------------
>
> Key: CALCITE-850
> URL: https://issues.apache.org/jira/browse/CALCITE-850
> Project: Calcite
> Issue Type: Bug
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
>
> CALCITE-457 added pushing expressions in join conditions into projects below the join in the FilterJoinRule, so the expression would be computed beforehand and not in the join predicate.
> While this can be an interesting feature for some projects using Calcite, it is a different functionality and it should be a standalone independent rule. For instance, in Hive we do not want to enable it at the moment, as it causes some performance regressions in many test cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)