The short answer is that CalciteConnectionImpl is really complicated and if we made it public people would complain if we changed one iota.
I had assumed that the existing extension points (e.g. Schema) were sufficient. Creating a new public API is not something I take on lightly. If we need a new extension point because of an unmet need, let’s figure out something that will work for as many as possible of Calcite’s users. Julian On Feb 7, 2015, at 3:03 PM, Hartman, Trevor <[email protected]> wrote: > On a related note, why is CalciteConnectionImpl package-private? Due to this > restriction, I'm having to put my own code in a org.apache.calcite.jdbc > package in order to create an org.apache.calcite.avatica.Meta.Factory > implementation. > > e.g.: > https://github.com/devth/calcite-map-demo/blob/master/src/main/scala/org/apache/calcite/jdbc/MapConnectionFactory.scala > > Trevor > > > On February 4, 2015 at 2:23:15 PM, Hartman, Trevor > ([email protected]<mailto:[email protected]>) wrote: > > I am embedding avatica-server in my system to serve jdbc queries. Is this not > the intended use? > > Trevor
