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

AWS Neptune returns an inaccessible structured error response

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Done
    • None
    • 3.7.0, 3.6.1, 3.5.4
    • python
    • None

    Description

      AWS Neptune uses a JSON error object for its status message with error details and a dedicated error code. Currently this json object gets combined into the error message string. I propose that we store the status message as a field on the error to allow end-users to deserialize the json into a dictionary. 

      Example Neptune Errors

      GremlinServerError

      598: {"detailedMessage":"A timeout occurred within the script or was otherwise cancelled directly during evaluation of [efa5d37d-587c-4409-986a-688129d57e37]","code":"TimeLimitExceededException","requestId":"efa5d37d-587c-4409-986a-688129d57e37"}

      GremlinServerError

      500: {"detailedMessage":"Failed to complete Insert operation for a Vertex due to conflicting concurrent operations. Please retry. 1 transactions are currently rolling back.","code":"ConcurrentModificationException","requestId":"8946b938-8b75-4623-ac0f-5049bba92e8e"}{{}}

      Attachments

        Activity

          People

            spmallette Stephen Mallette
            curtiscook Curtis Cook
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: