[ https://issues.apache.org/jira/browse/CALCITE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325331#comment-15325331 ]
Josh Elser commented on CALCITE-1287: ------------------------------------- Added the TCK test in https://git1-us-west.apache.org/repos/asf?p=calcite.git;a=commit;h=113a034ec1689dd8313af5d2f2d2431f1e666eaa Will wait to hear back from Kevin before closing this as cannot-repro. He might have some critical details. > Potential wire compatibility issue with binary data > --------------------------------------------------- > > Key: CALCITE-1287 > URL: https://issues.apache.org/jira/browse/CALCITE-1287 > Project: Calcite > Issue Type: Test > Components: avatica > Affects Versions: avatica-1.8.0 > Reporter: Josh Elser > Assignee: Josh Elser > Fix For: avatica-1.9.0 > > > 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). -- This message was sent by Atlassian JIRA (v6.3.4#6332)