Hi Jan,
I just commented on the Calcite thread. Phoenix needs to know the
connection properties and for each subsequent RPC, needs to know from which
connection you came. Otherwise we wouldn't know your tenant ID when the
statement is run. Something like a connection or session ID would need to
be
Hi,
We are working on a calcite/avatica based "thin" JDBC driver very
similar to what Phoenix has done with for its QueryServer, and I am
looking for some feedback/options.
Avatica in its current state doesn't have an RPC call for "create
connection". As a consequence, connection properties (i.e.
