[
https://issues.apache.org/jira/browse/CALCITE-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308275#comment-17308275
]
Julian Hyde commented on CALCITE-4552:
--------------------------------------
Work in progress:
[julianhyde/4552-interpeter-close|https://github.com/julianhyde/calcite/tree/4552-interpeter-close].
> Interpreter does not 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
> Environment: 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.
> Reporter: Julian Hyde
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
