[
https://issues.apache.org/jira/browse/CALCITE-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204287#comment-15204287
]
Josh Elser commented on CALCITE-836:
------------------------------------
bq. The whole point of JDBC is to stop your application from becoming dependent
on the plumbing. And yes, Avatica is just plumbing.
Well, my gut reaction was that {{"server.version"}} is still a dependency on
Avatica itself (is that a well-defined constant somewhere?). It's a magic
string, but at least it isn't a compile time dependency to Avatica.
> Provide a way for the Avatica client to query the server versions
> -----------------------------------------------------------------
>
> Key: CALCITE-836
> URL: https://issues.apache.org/jira/browse/CALCITE-836
> Project: Calcite
> Issue Type: New Feature
> Components: avatica
> Reporter: Holman Lan
> Assignee: Josh Elser
> Fix For: avatica-1.8.0
>
>
> Currently there doesn't seem to be a way for Avatica clients to find out the
> Avatica RPC protocol version and versions of other server components.
> The use case here is to allow the Apache Phoenix clients to request the
> Avatica version, Phoenix version and HBase version from the Phoenix Query
> Server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
