[GEODE-4414] Support nulls in new client protocol

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Component/s: client/server
• Labels: pull-request-available
• Assignee: Unassigned
• Reporter: Galen O'Sullivan
• Created: 29/Jan/18 17:37
• Updated: 09/Apr/18 22:37
• Resolved: 22/Feb/18 19:08

Description

The new client protocol currently sort of supports nulls, by sending an EncodedValue that is not set, but there's no mention of this (as far as I can tell) and it's not explicit.

An example where we might need nulls is when a function returns a list of null sentinel values that are meaningful. To support this use case, we should add a null case to EncodedValue.

Issue Links

• links to: GitHub Pull Request #1437