You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Menshikov (JIRA)" <ji...@apache.org> on 2017/08/08 14:34:00 UTC
[jira] [Created] (IGNITE-5994)
IgniteInternalCache.invokeAsync().get() can return null
Alexander Menshikov created IGNITE-5994:
-------------------------------------------
Summary: IgniteInternalCache.invokeAsync().get() can return null
Key: IGNITE-5994
URL: https://issues.apache.org/jira/browse/IGNITE-5994
Project: Ignite
Issue Type: Bug
Reporter: Alexander Menshikov
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:
```Java
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());
```
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)