You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Curtis Cook (Jira)" <ji...@apache.org> on 2022/06/22 17:34:00 UTC
[jira] [Created] (TINKERPOP-2764) AWS Neptune returns an inaccessible structured error response
Curtis Cook created TINKERPOP-2764:
--------------------------------------
Summary: AWS Neptune returns an inaccessible structured error response
Key: TINKERPOP-2764
URL: https://issues.apache.org/jira/browse/TINKERPOP-2764
Project: TinkerPop
Issue Type: Improvement
Components: python
Reporter: Curtis Cook
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
h5. 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"}
h5. 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"}{{}}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)