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

Posted to issues@calcite.apache.org by "Liya Fan (Jira)" <ji...@apache.org> on 2021/09/09 07:31:00 UTC

[jira] [Resolved] (CALCITE-4747) it seemes that collecGarbage in HepPlanner dose not clean outdated edges?

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

Liya Fan resolved CALCITE-4747.
-------------------------------
    Resolution: Fixed

Fixed by https://github.com/apache/calcite/pull/2501

> it seemes that collecGarbage in HepPlanner dose not clean outdated edges?
> -------------------------------------------------------------------------
>
>                 Key: CALCITE-4747
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4747
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Jianhui Dong
>            Priority: Minor
>              Labels: pull-request-available
>         Attachments: image-2021-08-19-12-12-41-534.png
>
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
>   !image-2021-08-19-12-12-41-534.png!
> After we use HepPlanner to optimize the RelNode,  we need to replace old RelNode with the optimized RelNode, and update the graph in HepPlanner, but calcite only remove the outdated RelNode(HepRelVertex) in line 970, the edges between these vertices are still in the graph, which may cause a memory leak? IMO, I think maybe we should also remove the outdated edge.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)