[
https://issues.apache.org/jira/browse/CALCITE-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059493#comment-15059493
]
James Taylor commented on CALCITE-767:
--------------------------------------
bq. FWIW, I'm about to implement PHOENIX-2411 which would support the "dumb"
load balancer scenario you mentioned.
Some work would be required in Avatica to support this scenario. Phoenix would
give you the transactional context as a result of executing a statement and
you'd need to pass this through the RPC. I think you'd need to do the same for
the connection URL and properties (though these wouldn't be modified by
Phoenix, just read).
If you want a lesson in "how to interpret Pherf numbers", [~mujtabachohan] is
your man.
> 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
> Components: avatica
> Reporter: Lukas Lalinsky
> Assignee: Josh Elser
> Fix For: next
>
>
> 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)
