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/06/24 23:32:05 UTC

[jira] [Moved] (CALCITE-767) Commit functionality not exposed by the RPC server

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

Nick Dimiduk moved PHOENIX-2071 to CALCITE-767:
-----------------------------------------------

    Workflow: jira  (was: patch-available, re-open possible)
         Key: CALCITE-767  (was: PHOENIX-2071)
     Project: Calcite  (was: Phoenix)

> Commit functionality not exposed by the RPC server
> --------------------------------------------------
>
>                 Key: CALCITE-767
>                 URL: https://issues.apache.org/jira/browse/CALCITE-767
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Lukas Lalinsky
>
> It seems that the commit/rollback functionality is not exposed by the RPC server, which means that it's only usable in autocommit mode. Avatica itself doesn't have a concept of commit in the RPC and the remote JDBC connection raises an exception when calling commit() on it, but Phoenix's native JDBC connection does implement commit(), so the RPC needs to be extended to allow calling that remotely.
> The easiest way to test this, "!autocommit off" and then "!commit" fails in "sqline-thin.py", but works in "sqline.py".



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