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

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2018/04/22 02:18:00 UTC

[jira] [Updated] (CALCITE-1949) CalciteStatement should call AvaticaStatement.close_(), to avoid memory leak

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

Julian Hyde updated CALCITE-1949:
---------------------------------
    Summary: CalciteStatement should call AvaticaStatement.close_(), to avoid memory leak  (was: CalciteStatement leads memory leak)

> CalciteStatement should call AvaticaStatement.close_(), to avoid memory leak
> ----------------------------------------------------------------------------
>
>                 Key: CALCITE-1949
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1949
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.13.0, 1.12.0, 1.11.0
>            Reporter: fuping.wang
>            Assignee: Kevin Risden
>            Priority: Major
>             Fix For: 1.17.0
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> CalciteStatement entends AvaticaStatement and  overrides the close_ method which didn't call  his parent's close_ method.    In AvaticaStatement , the close_ method remove the handler info from connection  which  make sure we don't leak on our side.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)