[
https://issues.apache.org/jira/browse/CALCITE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379005#comment-14379005
]
Nick Dimiduk commented on CALCITE-640:
--------------------------------------
Guava's
[Cache|http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/cache/Cache.html]
class doesn't let you override the expiration conditions for individual
values. I think we'll have to extend/implement our own Cache to achieve this
goal, or maybe add a daemon thread that trolls the cache on some interval,
honoring custom key settings. For now, let's leaving the cache duration as a
configuration setting specified by the operator at server launch time.
> 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)
