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.