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

Posted to issues@ignite.apache.org by "Ivan Bessonov (Jira)" <ji...@apache.org> on 2021/09/03 10:50:00 UTC

[jira] [Commented] (IGNITE-15338) Change storage API in Ignite 3 so that it returns null DataRow if entry is not found

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

Ivan Bessonov commented on IGNITE-15338:
----------------------------------------

Looks good to me

> Change storage API in Ignite 3 so that it returns null DataRow if entry is not found
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-15338
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15338
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Ivan Bessonov
>            Assignee: Aleksandr Polovtcev
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha3
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently methods like "org.apache.ignite.internal.storage.Storage#read" return non-null DataRow object that has null byte array in its value. This is not convenient and should be fixed.
> It is proposed to return null instead in all such places.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)