You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Semyon Danilov (Jira)" <ji...@apache.org> on 2021/08/19 11:51:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Semyon Danilov updated IGNITE-15338:
------------------------------------
Summary: Change storage API in Ignite 3 so that it returns null DataRow if entry is not found (was: Change storage API in Ignite 3 so that it returns null DataRow is entry is not found)
> 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
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
>
> 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)