[
https://issues.apache.org/jira/browse/CALCITE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378706#comment-14378706
]
Nick Dimiduk commented on CALCITE-640:
--------------------------------------
Okay, how would the client request a timeout? Right now we implicitly create
connection objects the first time a client requests data. This is in order to
avoid RPCs. I see no timeout methods on the java.sql.Connection API.
java.sql.Statement has a setQueryTimeout method, but that's a timeout for query
execution, not for the lifetime of a statement preparation.
This random
[article|http://www.cubrid.org/blog/dev-platform/understanding-jdbc-internals-and-timeout-configuration/]
> Avatica server should expire stale connections/statements
> ---------------------------------------------------------
>
> Key: CALCITE-640
> URL: https://issues.apache.org/jira/browse/CALCITE-640
> Project: Calcite
> Issue Type: Improvement
> Reporter: Nick Dimiduk
> Assignee: Julian Hyde
> Labels: avatica
> Fix For: next
>
> Attachments: 640.txt
>
>
> To avoid resource leaks in a long-running server process, we should be
> expiring our connections and statement handles after some configurable period.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
