Uploaded image for project: 'Calcite'
  1. Calcite
  2. CALCITE-1756

Implicit and explicit "null" not handled correctly with protobuf

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: avatica-1.10.0
    • Component/s: avatica
    • Labels:
      None

      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).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                elserj Josh Elser
                Reporter:
                elserj Josh Elser
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: