Details
-
Test
-
Status: Closed
-
Major
-
Resolution: Cannot Reproduce
-
avatica-1.8.0
-
None
Description
Was chatting with kliew today who mentioned that he thought there might be an issue with the wire-protocol with binary data (TypedValue.BYTE_STRING).
avatica-1.8.0 did contain a change to how binary data was sent using protobufs (reported by francischuang in CALCITE-1209, ultimately fixed in CALCITE-1103), but I believe this was done in a backwards compatible way.
I just added a test to the TCK which shows that it is compatible with 1.6.0 and 1.7.1, but maybe there is an edge condition I'm over looking (or the Java driver is masking).