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

["Lukas Lalinsky (JIRA)" <ji...@apache.org>]

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

Lukas Lalinsky commented on CALCITE-767:
----------------------------------------

Ah, I was not sure if that wasn't intentionally not implemented in Calcite with the idea that projects that need that should extend the interface. But adding full JDBC interface there makes more sense.

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