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

Posted to issues@calcite.apache.org by "Chunhui Shi (JIRA)" <ji...@apache.org> on 2018/05/02 01:18:00 UTC

[jira] [Commented] (CALCITE-2291) Add rule to push Project past Correlate

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

Chunhui Shi commented on CALCITE-2291:
--------------------------------------

I have a proposed fix for this. [https://github.com/apache/calcite/pull/685]

The main difference from ProjectJoinTransposeRule is the update to requiredColumns after the new project expressions are updated.

Another modification required is that the ANTI and SEMI are handled as LEFT in PushProjector when it is going to create strongBitmap in the fix. Could you review it? Thanks. [~julianhyde]

 

> Add rule to push Project past Correlate
> ---------------------------------------
>
>                 Key: CALCITE-2291
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2291
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Chunhui Shi
>            Assignee: Julian Hyde
>            Priority: Major
>
> Correlate is not derived from Join so we need a rule similar to ProjectJoinTransposeRule to push Project to under Correlate.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)