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

Julian Hyde commented on CALCITE-663:
-------------------------------------

The design was a straw man. It sounds as if you know how you would solve this - 
I'm happy to go with your proposal.

Do we want to get this (or part of this) into Calcite 1.2? We have about 24 
hours before RC 1.

> Would it be better to have a means for feature inspection? 

Yes. I would keep version, as a convenient short-hand for a list of methods, 
but also allow individual features to be described.

> One goal we have is to allow for session-less utilization of the query server.

That's a big one. We should discuss in a separate JIRA case. I was thinking we 
could allow a single round-trip to include a batch of requests, say 
[CreateConnection, CreateStatement, ExecuteStatement, Fetch] and have some way 
for request N to refer to IDs generated by requests 0..N-1.

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

Reply via email to