You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Hongze Zhang (JIRA)" <ji...@apache.org> on 2019/04/29 17:15:08 UTC

[jira] [Closed] (CALCITE-1205) Inconsistency in protobuf TypedValue field names

     [ https://issues.apache.org/jira/browse/CALCITE-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hongze Zhang closed CALCITE-1205.
---------------------------------

The issue was resolved but not closed in the given fix version. Closing now.

> Inconsistency in protobuf TypedValue field names 
> -------------------------------------------------
>
>                 Key: CALCITE-1205
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1205
>             Project: Calcite
>          Issue Type: Bug
>          Components: avatica
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: avatica-1.8.0
>
>
> [~francischuang] pointed out over in CALCITE-1192 that the "byte array" field in the protobuf TypedValue message has the name "bytes_values" instead of "bytes_value". Plural here does not make sense (as it is a single collection of bytes, not multiple collections of bytes).
> Changing the field name will not have an affect on binary compatibility, so I'm going to go ahead and make that change. The java API will change ever-so-slightly, but we haven't defined what our Java API is truly comprised of and to what degree we are providing stability, so we'll just ignore that for now.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)