Josh Elser created CALCITE-1756:
-----------------------------------
Summary: Implicit and explicit "null" not handled correctly with
protobuf
Key: CALCITE-1756
URL: https://issues.apache.org/jira/browse/CALCITE-1756
Project: Calcite
Issue Type: Bug
Components: avatica
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: avatica-1.10.0
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).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
