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 2019/02/08 23:35:00 UTC

[jira] [Commented] (CALCITE-1045) Decorrelate sub-queries in Project and Join

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

Chunhui Shi commented on CALCITE-1045:
--------------------------------------

What is the progress of this work?

> Decorrelate sub-queries in Project and Join
> -------------------------------------------
>
>                 Key: CALCITE-1045
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1045
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>            Priority: Major
>              Labels: sub-query
>
> In CALCITE-816 we created a representation of sub-query in the relational algebra, RexSubQuery, so that we could defer expanding and de-correlating sub-queries until after SqlNode tree has been converted to RelNode tree. But the RelDecorrelator can only reliably handle sub-queries that occur in a Filter (such as WHERE EXISTS or WHERE IN).
> This task would except RelDecorrelator to handle sub-queries in Project (which occur with scalar sub-queries in the SELECT clause) and sub-queries in Join (which occur with scalar sub-queries in the ON clause of a JOIN).



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