You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Mihai Budiu (Jira)" <ji...@apache.org> on 2025/05/17 00:33:00 UTC

[jira] [Assigned] (CALCITE-7023) Create an optimization pass which can decorrelate subplans

     [ https://issues.apache.org/jira/browse/CALCITE-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mihai Budiu reassigned CALCITE-7023:
------------------------------------

    Assignee: Mihai Budiu

> Create an optimization pass which can decorrelate subplans
> ----------------------------------------------------------
>
>                 Key: CALCITE-7023
>                 URL: https://issues.apache.org/jira/browse/CALCITE-7023
>             Project: Calcite
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.39.0
>            Reporter: Mihai Budiu
>            Assignee: Mihai Budiu
>            Priority: Minor
>
> Today the Calcite decorrelator attempts to decorrelate an entire query tree; if it fails, it returns the tree unchanged. However, sometimes a query tree can contain multiple subtrees rooted by Correlate nodes, some of which can be decorrelated using the existing decorrelator.
> One can write an optimization rule which can attempt to apply the decorrelator to subtrees rooted at Correlate nodes which do not have any Correlate children.
> This "incremental" decorrelation strategy may manage to decorrelate queries that otherwise would fail.
> The naive approach would strip the subtree before invoking the decorrelator. Maybe there is a better way to do this, but using the decorrelator as a black box is easy. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)