You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2015/07/01 02:37:10 UTC

[jira] [Updated] (CALCITE-745) Connection and statement cache container to remain in sync for Avatica

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

Nick Dimiduk updated CALCITE-745:
---------------------------------
    Component/s: avatica

Bulk edit assigning avatica component to obvious issues.

> Connection and statement cache container to remain in sync for Avatica
> ----------------------------------------------------------------------
>
>                 Key: CALCITE-745
>                 URL: https://issues.apache.org/jira/browse/CALCITE-745
>             Project: Calcite
>          Issue Type: Improvement
>          Components: avatica
>            Reporter: Xavier FH Leong
>            Assignee: Julian Hyde
>              Labels: avatica
>
> Currently, the statement and connection cache are remain separate, I see a problem during invalidation of cache if they are kept apart, connection may close first before statement and making statement retrieved from statement cache being staled. One way is to extend the connection cache to include data structure that also store statement map, and there only remain a single cache policy. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)