[
https://issues.apache.org/jira/browse/CALCITE-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213347#comment-15213347
]
Julian Hyde commented on CALCITE-836:
-------------------------------------
I still believe we should not make an application depend on an Avatica class if
it wants to get extra information from the server side. But as I understand it,
you would require people to write
{{metadata.unwrap(AvaticaDatabaseMetaData.class)}. Could you allow, *in
addition to this*, {{metadata.unwrap(Properties.class)}}.
FilteredConstants needs javadoc. AvaticaDatabaseMetaData needs better javadoc.
(How would you get hold of an instance?)
> 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)
