[
https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16125183#comment-16125183
]
Josh Elser commented on CALCITE-1938:
-------------------------------------
bq. I'd definitely keep the tests running against Phoenix at the very least
since the driver advertises Phoenix support
Support for Phoenix's use of Avatica should be secondary to making sure that it
works against Avatica "proper".
bq. It's possible to duplicate the tests and run them twice, once on Phoenix
and once on avatica + hsqldb, but I am wondering if the payoff is worth it
(tests would probably take twice as long to run).
Couldn't something be done to figure out the flavor of database and what it
supports? I think we have driver information already sent back from the server.
Maybe it's as simple as returning that back? Syntax shouldn't matter for the
driver itself, just the sql provided, no?
Anyways, I don't think it's a good use of our time to try to deploy a full
hbase installation on the ASF infra. It tends to be over-taxed already -- a
minimal testing environment is the best plan of action.
> First Apache release for Avatica Go
> -----------------------------------
>
> Key: CALCITE-1938
> URL: https://issues.apache.org/jira/browse/CALCITE-1938
> Project: Calcite
> Issue Type: Bug
> Components: avatica-go
> Reporter: Julian Hyde
> Assignee: Francis Chuang
>
> Make a release for Avatica Go.
> Release number is TBD.
> This will be the first Apache release for Avacica Go, so expect more
> diligence / issues than usual.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
