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/10/23 20:57:27 UTC
[jira] [Commented] (CALCITE-663) Add CreateConnectionRequest and
protocol version to Avatica protocol
[ https://issues.apache.org/jira/browse/CALCITE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14971623#comment-14971623 ]
Julian Hyde commented on CALCITE-663:
-------------------------------------
The "Add CreateConnectionRequest" part of this is fixed in CALCITE-912, OpenConnectionRequest.
Changing summary to reflect remaining work.
[~elserj], [~ndimiduk], Is the protocol version solved?
> Add CreateConnectionRequest and protocol version to Avatica protocol
> --------------------------------------------------------------------
>
> Key: CALCITE-663
> URL: https://issues.apache.org/jira/browse/CALCITE-663
> Project: Calcite
> Issue Type: Bug
> Components: avatica
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Labels: avatica
>
> Add protocol version to Avatica protocol, to allow forwards and backwards compatibility.
> The first request should be a CreateConnectionRequest, let's add the attributes there. I propose:
> * CreateConnectionRequest.requestedProtocolType e.g. "json"
> * CreateConnectionRequest.requestedProtocolVersion e.g. "1.2.0"
> * CreateConnectionRequest.driverVersion
> * CreateConnectionRequest.driverName e.g. "org.apache.calcite.avatica.remote.Driver"
> * CreateConnectionResponse.protocolType
> * CreateConnectionResponse.protocolVersion
> * CreateConnectionResponse.databaseVersion
> There is currently no CreateConnectionRequest.
> Certain servers configurations would continue to allow connections to be implicitly created, but using an explicit CreateConnectionRequest would always be possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)