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 2015/03/24 03:14:53 UTC

[jira] [Commented] (CALCITE-640) Avatica server should expire stale connections/statements

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

Julian Hyde commented on CALCITE-640:
-------------------------------------

That "configurable period" should be the connection/statement timeout requested by the JDBC client. 

A server should have sensible default timeouts. And maybe as a policy a server might disallow timeouts that are too long.

> 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
>
> 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)