New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TINKERPOP-1913 Make status attributes available #933
Conversation
Test graphs are now named differently given the refactoring that went into improving integration configurations. Also fixed a bug in NO_CONTENT messages and added a test.
Didn't seem necessary to set them directly into a member variable on ResultQueue when they could be passed more safely by just including them with the completion state update
Adds StatusAttributes property on ResponseException. Removed explicit this from ResultSet<T> to align with existing style.
Thanks for taking this forward. When can we expect the rc2 nuget package? |
Assuming there are no objections on the dev list to doing a release candidate for 3.4.0 then it could be as early as next week, but that discussion needs to run to completion. Please follow along here: |
VOTE +1 |
1 similar comment
VOTE +1 |
This is a great step. Now that #922 - TINKERPOP-1959 has been closed, when would we expect to see ResultSets containing the necessary attributes in gremlin-javascript? That's super interesting for surfacing performance stats to the various clients :). |
I just created this: https://issues.apache.org/jira/browse/TINKERPOP-2064 in reference to gremlin-javascript |
https://issues.apache.org/jira/browse/TINKERPOP-1913
Status attributes have always been returned from Gremlin Server but they haven't been easy to access unless you were working with the lower end of the protocol. They are now available in a fairly wide number of ways across most of the various drivers in a fairly consistent fashion. The current gap in this feature is related to gremlin-javascript probably needs #922 - TINKERPOP-1959 so that we even have a "ResultSet" of sorts to hold the status attributes and make them available.
Note that the travis error seems to be weirdness in travis:
don't think that's anything that's really failing.
All tests pass with
docker/build.sh -t -n -i
VOTE +1