You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Swapnil Bawaskar (JIRA)" <ji...@apache.org> on 2018/04/09 22:37:29 UTC

[jira] [Closed] (GEODE-4414) Support nulls in new client protocol

     [ https://issues.apache.org/jira/browse/GEODE-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Swapnil Bawaskar closed GEODE-4414.
-----------------------------------

> Support nulls in new client protocol
> ------------------------------------
>
>                 Key: GEODE-4414
>                 URL: https://issues.apache.org/jira/browse/GEODE-4414
>             Project: Geode
>          Issue Type: New Feature
>          Components: client/server
>            Reporter: Galen O'Sullivan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.5.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)