[jira] [Resolved] (CALCITE-1118) "noop" JDBC driver for benchmarking/testing Avatica

["Josh Elser (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CALCITE-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser resolved CALCITE-1118.
---------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: next)
                   1.7.0

Fixed in https://git1-us-west.apache.org/repos/asf?p=calcite.git;a=commit;h=d27e642c497d406474fd8b543d74836152e8696c

> "noop" JDBC driver for benchmarking/testing Avatica
> ---------------------------------------------------
>
>                 Key: CALCITE-1118
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1118
>             Project: Calcite
>          Issue Type: Sub-task
>          Components: avatica
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
>
>
> As I was working on the general effort of improving performance of Avatica (alluded to in CALCITE-1117), I found myself lamenting a view into the performance of Avatica that wasn't bound by the underlying database being written to.
> I hacked together a really quick/dirty JDBC driver that does nothing whenever you call the methods (sans creating Statements and DatabaseMetaData instances). Turns out this was really useful in testing our *just* Avatica.
> I'm sure there are issues with it, but it was sufficient for doing some write-heavy testing. Would be nice to have it included for future testing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)