That's not true. You can use a Schema from multiple connections. Obviously you're responsible for thread safety if the Schema is mutable.
Julian > On Sep 17, 2017, at 11:49 PM, Christian Beikov <[email protected]> > wrote: > > I might be wrong, but as far as my knowledge goes, you can't have more than > a single connection to the same schema right now. I am planning to work on > that soon by implementing a datasource. As part of that I would take a look > at how Aviatica's remote capabilities fit into. Until then, I'd rather > stick to testing for now. > > Regards, > Christian > > > Am 18.09.2017 8:36 vorm. schrieb "Nick Stephen" <[email protected]>: > > Hi folks, > > We’ve started experimenting with Calcite for some work and have been > running it in-process using a datasource wrapped around a local connection > (using jdbc:calcite). > > I’d now like to expose this same database remotely using avatica, but can’t > see any APIs in avatica which can take a Connection object. If I create a > Meta with the same local URL then I understandably get a different DB > instance. > > Could someone point out the appropriate API, or are there any examples of > exposing a calcite DB remotely using avatica whilst still being able to use > it locally in-process to avoid the additional network hop. > > Thanks! > > Nick
