Attach rawMessage property to error on execute() #105
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! That makes sense. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some gremlin-compatible endpoints (such as Azure CosmosDB Graph) provide additional metadata in the message which is useful for processing. It's possible to retrieve this information using a custom
executeHandler, but the metadata is swallowed when an error occurs, making it impossible for a client to retrieve it.This change adds a
rawMessageproperty to the error emitted so that clients can retrieve additional structured information from the message when errors occur. I'm also open to any suggestions for other approaches/field names. I went with this because it was simple and non-breaking without limiting the available information.