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

Yakov Zhdanov commented on IGNITE-5994:
---------------------------------------

Currently {{invokeAsync()}} is defined as {{public <T> IgniteFuture<T> 
invokeAsync(.....)}}.

If we need EntryProcessorResult to be returned from Future then it should be 
{{public <T> IgniteFuture<EntryProcessorResult<T>> invokeAsync(.....)}}. I am 
not sure why we have this difference in sync/async counterpart. Probably, 
[~vozerov] or [~tledkov-gridgain] can provide some info.

I also think that we will not changing the public API in 2.0. Let's leave it as 
is and then fix in next major version.


> 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
>            Priority: Minor
>              Labels: newbie
>         Attachments: IgniteCacheSelfTest.java
>
>
> 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
(v6.4.14#64029)

Reply via email to