[
https://issues.apache.org/jira/browse/IGNITE-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734576#comment-14734576
]
ASF GitHub Bot commented on IGNITE-1388:
----------------------------------------
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/75
IGNITE-1388 Platform .Net: cache.Invoke result in async mode should have an
error flag
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-1388
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/75.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #75
----
commit 57555af62c93bdc8e012c1be7b6c6edd4d9d2ebe
Author: ptupitsyn <[email protected]>
Date: 2015-09-08T10:25:18Z
IGNITE-1388 Platform .Net: cache.Invoke result in async mode should have an
error flag
----
> Platform .Net: cache.Invoke result in async mode should have an error flag
> --------------------------------------------------------------------------
>
> Key: IGNITE-1388
> URL: https://issues.apache.org/jira/browse/IGNITE-1388
> Project: Ignite
> Issue Type: Bug
> Components: interop
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Fix For: ignite-1.4
>
>
> In async mode we either write a result directly, or use
> EntryProcessorExceptionWriter in case of an error. It is impossible to
> discern an error from good result on the receiving end. Need to write a flag
> first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
