Per thread on dev list titled "Avatica handling of connection state", this ticket implements such an rpc.
I have a hunch that in the longer term we may want to combine several kinds of modifications (to connection, statement, result set) but I may be wrong, so it's better to go for Nick Dimiduk's more straightforward scheme.
Nick can you mark ConnectionProperties as experimental, add some tests, and I'll commit.
Sure, I can comment as experimental.
I have a new patch that make connectionSync lazy for RemoteMeta, will post shortly. Adding test coverage is not possible at the moment, because all the juicy bits are in RemoteMeta, which is not instantiated in the current framework of RemoteDriverTest. Further, due to package protections, it seems blocked by the lack of CALCITE-652. Let me do that work, then rebase.
Parking a patch pre-rebase of CALCITE-652. It makes connectionSyn a lazy RPC call in RemoteMeta (though still a 2nd RPC, rather than piggy-backing on associated data RPC), converts Meta.ConnectionProperties into an interface, and adds the comments regarding interface stability.
Adds test coverage.
Patch created on top of other refactoring changes, see https://github.com/ndimiduk/incubator-calcite/tree/avatica-to-prod
Fixed in http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/304eb70c.
Resolved in release 1.2.0-incubating (2015-04-16)