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/09/14 08:01:00 UTC
[jira] [Commented] (IGNITE-6250) .NET: Thin client: Exception
handling
[ https://issues.apache.org/jira/browse/IGNITE-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165926#comment-16165926 ]
Pavel Tupitsyn commented on IGNITE-6250:
----------------------------------------
We need a way to include maximum amount of details in exceptions.
For example, exception can happen in .NET ScanQuery filter, then be rethrown in Java. We have {{PlatformNativeException}} which contains serialized platform exception.
So the format can be defined like this:
* {{string exceptionClass}}
* {{string exceptionMessage}}
* {{string stackTrace}}
* {{object data}}
* {{bool hasCause}} - if yes, start reading again
> .NET: Thin client: Exception handling
> -------------------------------------
>
> Key: IGNITE-6250
> URL: https://issues.apache.org/jira/browse/IGNITE-6250
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> Exception handling in thin client: response includes a success flag. Define exception format protocol in case of failure.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)