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

Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/02/22 19:08:00 UTC

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

    [ https://issues.apache.org/jira/browse/GEODE-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373264#comment-16373264 ] 

ASF subversion and git services commented on GEODE-4414:
--------------------------------------------------------

Commit 37ff71531d900c160f4d2e05042f509f96da60ef in geode's branch refs/heads/develop from [~WireBaron]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=37ff715 ]

GEODE-4414: Support explicit nulls in geode's protobuf protocol (#1437)



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