[
https://issues.apache.org/jira/browse/TINKERPOP-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16636683#comment-16636683
]
stephen mallette edited comment on TINKERPOP-1906 at 10/3/18 9:36 AM:
----------------------------------------------------------------------
This was added on TINKERPOP-1913
https://github.com/apache/tinkerpop/blob/b788201bfcc0bd4f2a5eb24a66d32be58d06583d/gremlin-dotnet/src/Gremlin.Net/Driver/Exceptions/ResponseException.cs#L57
was (Author: spmallette):
This was added on TINKERPOP-1906
https://github.com/apache/tinkerpop/blob/b788201bfcc0bd4f2a5eb24a66d32be58d06583d/gremlin-dotnet/src/Gremlin.Net/Driver/Exceptions/ResponseException.cs#L57
> Make ResponseException explorable
> ---------------------------------
>
> Key: TINKERPOP-1906
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1906
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet
> Affects Versions: 3.2.7
> Reporter: Roman Kreisel
> Assignee: stephen mallette
> Priority: Major
> Fix For: 3.4.0
>
> Attachments: message.txt, stacktrace.txt
>
>
> The ResponseException from Gremlin.NET doesn't give you any possibility to
> react on the GremlinService's Response. The only content is the exception's
> Message, which is just free text.
> It would be great, to add some fields to expose at least the HTTP ErrorCode
> or anything else that's responded by the service.
>
> Especially, if you're using Gremlin.NET with Azure's Cosmos DB, there's a
> "Request Rate to Large" response, in case you have high load on your
> database. In such a case, you want to be able to detect this "error" and just
> retry after a few milliseconds (i'm not sure, but i think even a proposal for
> this retry-timeout is given in the response)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)