You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2017/05/02 19:35:04 UTC

[jira] [Created] (IGNITE-5137) .NET: Propagate native ScanQuery exceptions

Pavel Tupitsyn created IGNITE-5137:
--------------------------------------

             Summary: .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
             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, but not for ScanQuery, where only exception message gets propagated (which complicates debugging).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)