Return-Path: X-Original-To: apmail-ignite-issues-archive@minotaur.apache.org Delivered-To: apmail-ignite-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 76BFA10F46 for ; Tue, 8 Sep 2015 10:16:00 +0000 (UTC) Received: (qmail 59003 invoked by uid 500); 8 Sep 2015 10:15:47 -0000 Delivered-To: apmail-ignite-issues-archive@ignite.apache.org Received: (qmail 58970 invoked by uid 500); 8 Sep 2015 10:15:47 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 58959 invoked by uid 99); 8 Sep 2015 10:15:47 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Sep 2015 10:15:47 +0000 Date: Tue, 8 Sep 2015 10:15:47 +0000 (UTC) From: "Pavel Tupitsyn (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-1388) Platform .Net: cache.Invoke result in async mode should have an error flag MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Pavel Tupitsyn created IGNITE-1388: --------------------------------------- Summary: 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)