Uploaded image for project: 'TinkerPop'
  1. TinkerPop
  2. TINKERPOP-1906

Make ResponseException explorable

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Done
    • 3.2.7
    • 3.4.0
    • dotnet
    • None

    Description

      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)

      Attachments

        1. stacktrace.txt
          1 kB
          Roman Kreisel
        2. message.txt
          2 kB
          Roman Kreisel

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            spmallette Stephen Mallette
            RomanKreisel Roman Kreisel
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment