[
https://issues.apache.org/jira/browse/CALCITE-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200717#comment-15200717
]
Julian Hyde commented on CALCITE-836:
-------------------------------------
We could expose the extra properties as a (name, value) map, and define some
properties that we suggest every Avatica provider implements. It's a shame that
the DatabaseMetaData API doesn't allow any extension properties. Rather than
adding an API to DatabaseMetaData, maybe we can make clever use of the
{{unwrap}} method, like this:
{code}
Connection connection;
DatabaseMetaData metaData = connection.getMetaData();
Properties properties = metaData.unwrap(Properties.class);
String serverVersion = properties == null ? null :
properties.getProperty("server.version");
{code}
> 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)
