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 2021/03/28 04:17:00 UTC

[jira] [Updated] (CALCITE-4552) Interpreter should close resources held by its Nodes on close

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

Julian Hyde updated CALCITE-4552:
---------------------------------
    Summary: Interpreter should close resources held by its Nodes on close  (was: Interpreter does not close resources held by its Nodes on close)

> Interpreter should close resources held by its Nodes on close
> -------------------------------------------------------------
>
>                 Key: CALCITE-4552
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4552
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Priority: Major
>
> When closing Interpreter, close resources held by its Nodes.
> Currently, if a node is based on a JdbcTableScan, and the Interpreter's results have not been read to completion, the statement will still be open, and the JDBC connection will not be returned to the pool. This can cause a hang, waiting for a connection, if you allocate and deallocate lots of Interpreter instances.



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