You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2022/10/04 10:52:00 UTC
[jira] [Resolved] (CALCITE-1045) Decorrelate sub-queries in Project and Join
[ https://issues.apache.org/jira/browse/CALCITE-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stamatis Zampetakis resolved CALCITE-1045.
------------------------------------------
Fix Version/s: 1.33.0
Assignee: Benchao Li
Resolution: Fixed
All test cases that were skipped with {{fixed.calcite1045}} are passing in https://github.com/apache/calcite/commit/c2407f59c32d1690d16b641d556bb27f8f1783ac thus I am marking this as resolved.
> 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: Benchao Li
> Priority: Major
> Labels: pull-request-available, sub-query
> Fix For: 1.33.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)