ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Muzafarov (Jira)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-5994) IgniteInternalCache.invokeAsync().get() can return null
Date Thu, 10 Oct 2019 13:12:08 GMT

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

Maxim Muzafarov updated IGNITE-5994:
------------------------------------
    Fix Version/s: 2.8

> IgniteInternalCache.invokeAsync().get() can return null
> -------------------------------------------------------
>
>                 Key: IGNITE-5994
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5994
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.1
>            Reporter: Alexander Menshikov
>            Assignee: Alexander Menshikov
>            Priority: Minor
>              Labels: newbie
>             Fix For: 2.8
>
>         Attachments: IgniteCacheSelfTest.java, master_8629b50d6f_ignite-5994.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The IgniteInternalCache.invoke() always return an EntryProcessorResult, but the IgniteInternalCache.invokeAsync().get()
can return the null in case when an EntryProcessor has returned the null.
> Code from reproducer:
> {noformat}
> final EntryProcessor<Object, Object, Object> ep = new EntryProcessor<Object,
Object, Object>() {
>             @Override
>             public Object process(MutableEntry<Object, Object> entry,
>                 Object... objects) throws EntryProcessorException {
>                 return null;
>             }
>         };
>         EntryProcessorResult<Object> result = utilCache.invoke("test", ep);
>         assertNotNull(result);
>         assertNull(result.get());
>         result = utilCache.invokeAsync("test", ep).get();
>         // Assert here!!!
>         assertNotNull(result);
>         assertNull(result.get());
> {noformat}
> It can be optimization. Nevertheless results of invoke() must be equals with results
of invokeAsync().get(). So there are two options:
> 1) To do so would be the invokeAsync(key, ep).get() returned the null too for the optimization.
> 2) Or to do so would be the invoke(key, ep) returned an EntryProcessorResult for a logical
consistency.
> NOTE: Don't confuse with IgniteCache.invoke.



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

Mime
View raw message