[
https://issues.apache.org/jira/browse/CALCITE-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204996#comment-15204996
]
Julian Hyde commented on CALCITE-836:
-------------------------------------
It's (to coin a phrase) a "specification dependency", which is one of the best
kinds of dependency because it doesn't cause link errors. :)
For instance, you could change MySQL's JDBC server (which does not use Avatica)
to emit a "server.version" property if someone were to call
{{unwrap(Map.class).get("server.version")}} on its driver. It would not need to
include any Avatica code. It would just require one of the MySQL developers to
have read the Avatica specification and thought "hey, that's a good idea".
> 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)
