Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 45288200CA3 for ; Tue, 2 May 2017 21:36:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 43AA4160BAB; Tue, 2 May 2017 19:36:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8E36F160BBE for ; Tue, 2 May 2017 21:36:08 +0200 (CEST) Received: (qmail 33848 invoked by uid 500); 2 May 2017 19:36:07 -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 33837 invoked by uid 99); 2 May 2017 19:36:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 May 2017 19:36:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 66E4FC0DC3 for ; Tue, 2 May 2017 19:36:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 9hE7y-8sKNgt for ; Tue, 2 May 2017 19:36:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2290E5F1BA for ; Tue, 2 May 2017 19:36:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 00AE4E0D4E for ; Tue, 2 May 2017 19:36:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 51FBA21DE9 for ; Tue, 2 May 2017 19:36:04 +0000 (UTC) Date: Tue, 2 May 2017 19:36:04 +0000 (UTC) From: "Pavel Tupitsyn (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-5137) .NET: Propagate native ScanQuery exceptions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 02 May 2017 19:36:09 -0000 [ https://issues.apache.org/jira/browse/IGNITE-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-5137: ----------------------------------- Description: When exception occurs in user callback on .NET side we should serialize it entirely, send to caller node and re-throw there (wrapping in IgniteException) to preserve original stack trace. We already do this for Compute (see {{UnmanagedCallbacks.ComputeJobExecute}}), but not for ScanQuery, where only exception message gets propagated (which complicates debugging). was: When exception occurs in user callback on .NET side we should serialize it entirely, send to caller node and re-throw there (wrapping in IgniteException) to preserve original stack trace. We already do this for Compute, but not for ScanQuery, where only exception message gets propagated (which complicates debugging). > .NET: Propagate native ScanQuery exceptions > ------------------------------------------- > > Key: IGNITE-5137 > URL: https://issues.apache.org/jira/browse/IGNITE-5137 > Project: Ignite > Issue Type: Improvement > Components: platforms > Reporter: Pavel Tupitsyn > Labels: .NET > Fix For: 2.1 > > > When exception occurs in user callback on .NET side we should serialize it entirely, send to caller node and re-throw there (wrapping in IgniteException) to preserve original stack trace. > We already do this for Compute (see {{UnmanagedCallbacks.ComputeJobExecute}}), but not for ScanQuery, where only exception message gets propagated (which complicates debugging). -- This message was sent by Atlassian JIRA (v6.3.15#6346)