[CALCITE-1756] Implicit and explicit "null" not handled correctly with protobuf

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: avatica-1.10.0
• Component/s: avatica
• Assignee: Josh Elser
• Reporter: Josh Elser
• Created: 17/Apr/17 15:59
• Updated: 08/Jun/17 17:02
• Resolved: 24/Apr/17 22:14

Description

In finishing up the implementation for CALCITE-1050, I found that a unit test has been passing unintentionally.

When the user does not provide a value for an unbound parameter on a Statement, the code is supposed to fail server-side. However, this was actually failing client side for the protobuf path, due to Protobuf's avoidance of "null" values.

Need to make sure that we differentiate between explicitly null values (statement.setObject(1, null)) and implicitly null values (no value was set).

Issue Links

• is related to: CALCITE-1050 Avatica can't serialize java.sql.Array