[
https://issues.apache.org/jira/browse/CALCITE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14481690#comment-14481690
]
Nick Dimiduk commented on CALCITE-663:
--------------------------------------
bq. Do we want to get this (or part of this) into Calcite 1.2? We have about 24
hours before RC 1
We're not prepared to provide an implementation and validate it vs
backward/forward compatibility scenarios in 24 hours. No, I think 1.2 ships
without this.
> 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
> 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)
