[
https://issues.apache.org/jira/browse/CALCITE-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612771#comment-17612771
]
Stamatis Zampetakis commented on CALCITE-1045:
----------------------------------------------
[~jamesstarr] We discussed under CALCITE-5127 and agreed to close this ticket
as part of that change since all tests which were skipped with
fixed.calcite1045 are passing. I am pretty sure there are many more bugs to fix
but we could do it using new and more specific JIRAs.
Having said that if someone wants to keep this JIRA open for some reason, I'm
fine with that as well; don't have strong preferences.
> 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)
