[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=17612776#comment-17612776 ] Stamatis Zampetakis commented on CALCITE-1045: -- OK, I just remembered that there are more references to CALCITE-1045 in particular inside RelOptRulesTest so I am going to re-open this ticket. > 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)
[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=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)
[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=17612733#comment-17612733 ] James Starr commented on CALCITE-1045: -- [~zabetak], Great work, however, the fix looks to only address projects, and existing problems with outer joins. Were the problems with outer joins addressed in a different PR? > 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)
[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=17540588#comment-17540588 ] Benchao Li commented on CALCITE-1045: - Hi all, I found that https://issues.apache.org/jira/browse/CALCITE-5127 is related to this issue, and I implemented Projection Correlation in https://issues.apache.org/jira/browse/CALCITE-5127 Welcome reviewing~ > 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 >Priority: Major > Labels: pull-request-available, sub-query > 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.7#820007)
[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=17366827#comment-17366827 ] James Starr commented on CALCITE-1045: -- [~zabetak] , do you have any further feed back? > 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 >Priority: Major > Labels: pull-request-available, sub-query > Time Spent: 40m > 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.3.4#803005)
[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=17351156#comment-17351156 ] Stamatis Zampetakis commented on CALCITE-1045: -- I've noticed that there is a PR#2385 by [~jamesstarr] linked to this issue. I went quickly over the changes but I would appreciate some extra clarifications regarding the high-level goal of this PR. > 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 >Priority: Major > Labels: pull-request-available, sub-query > Time Spent: 20m > 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.3.4#803005)
[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=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)
[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=15099031#comment-15099031 ] Julian Hyde commented on CALCITE-1045: -- Work in progress at https://github.com/julianhyde/calcite/tree/1045-correlated-project. > 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 > > 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 (v6.3.4#6332)
[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=15086451#comment-15086451
]
Julian Hyde commented on CALCITE-1045:
--
When fixing this case, search for {{if (fixed.calcite1045)}} in .oq files.
> 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
>
> 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
(v6.3.4#6332)
