It does seem a bit strange that there are Meta implementations which wrap a single connection, while at the same time some Meta methods (createStatement) take a ConnectionHandle as parameter.
2015-09-30 17:41 GMT+02:00 Bruno Dumon <[email protected]>: > 2015-09-30 17:23 GMT+02:00 Bruno Dumon <[email protected]>: > >> Hi, >> >> I am looking into the same thing, and I think we need a "create >> connection" operation in the avatica rpc, since these properties are passed >> at connection creation time. Right now connections are implicitly created >> when the client passes an unknown connection id. >> >> On first sight the most logical place to do this is by adding a connect() >> method implementation to remote.Driver that performs the rpc to create the >> connection on the server. This would assume we have at that point access to >> Service.Factory, but that is not the case, as this is created by the >> Connection itself by calling Driver.createMeta(). Another issue is that it >> is the AvaticaConnection constructor which decides on the connection id. A >> solution might be to refactor this so that these things are created by the >> driver and passed to the connection constructor (via >> AvaticaFactory.newConnection), does this sound reasonable? >> > I overlooked the fact that some Meta implementations wrap the connection, > so it is not easily possible to reverse this. > > Ideas on how to approach adding a "create connection" rpc call definitely > welcome :-) > > -- > Bruno > >
