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/30 08:01:52 UTC

[jira] [Resolved] (CALCITE-636) Connection isolation for Avatica clients

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

Julian Hyde resolved CALCITE-636.
---------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: next)
                   1.2.0-incubating

Fixed in http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/0ad6019b.

> Connection isolation for Avatica clients
> ----------------------------------------
>
>                 Key: CALCITE-636
>                 URL: https://issues.apache.org/jira/browse/CALCITE-636
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Nick Dimiduk
>            Assignee: Julian Hyde
>              Labels: avatica
>             Fix For: 1.2.0-incubating
>
>         Attachments: CALCITE-636.00.patch
>
>
> Avatica should manage independent connections to it's underlying data source for each client connection. Clients should be isolated from each other, so that one's statements don't collide with another's.



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