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

Posted to issues@calcite.apache.org by "Chunwei Lei (Jira)" <ji...@apache.org> on 2019/09/09 06:48:00 UTC

[jira] [Commented] (CALCITE-3330) propagateCostImprovements() could result in stack overflow

    [ https://issues.apache.org/jira/browse/CALCITE-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16925409#comment-16925409 ] 

Chunwei Lei commented on CALCITE-3330:
--------------------------------------

It seems to be the same with CALCITE-2204.

> propagateCostImprovements() could result in stack overflow
> ----------------------------------------------------------
>
>                 Key: CALCITE-3330
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3330
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Xiening Dai
>            Assignee: Xiening Dai
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Current implementation uses depth first approach for propagating cost improvements to parent rel nodes. This could lead to stack overflow if the rel node hierarchy is very deep. Suggest use breath first approach for cost propagation. 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)