You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@calcite.apache.org by "Benchao Li (Jira)" <ji...@apache.org> on 2023/05/19 11:55:00 UTC

[jira] [Created] (CALCITE-5715) Prune old nodes after projection merging in ProjectionMergeRule

Benchao Li created CALCITE-5715:
-----------------------------------

             Summary: Prune old nodes after projection merging in ProjectionMergeRule
                 Key: CALCITE-5715
                 URL: https://issues.apache.org/jira/browse/CALCITE-5715
             Project: Calcite
          Issue Type: Improvement
          Components: core
    Affects Versions: 1.34.0
            Reporter: Benchao Li


We already have many similar usages (prune old nodes) to reduce the search scope, I propose to also add this for {{ProjectionMergeRule}}. Do you have any concerns about this?

The reason I propose to do this optimization for {{ProjectionMergeRule}} is that I met a problem that two sets will point to each other after projection merging, and the planner will run into dead loop. (It's hard to show the details, I haven't got a simple reproducible demo yet)



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