[CALCITE-1205] Inconsistency in protobuf TypedValue field names

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: avatica-1.8.0
• Component/s: avatica
• Assignee: Josh Elser
• Reporter: Josh Elser
• Created: 18/Apr/16 15:04
• Updated: 29/Apr/19 17:14
• Resolved: 18/Apr/16 15:22

Description

Francis Chuang 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.

Issue Links

• relates to: CALCITE-1192 Document protobuf and json REP types with examples