TINKERPOP-2070: Introduce Connection and ResultSet abstractions #966
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.
https://issues.apache.org/jira/browse/TINKERPOP-2070
Extract
Connection
implementation out of theDriverRemoteConnection
.The
DriverRemoteConnection
now uses aClient
instance, aClient
instance may contain one or moreConnection
instances, similar to the Python and .NET glv.Introduce
ResultSet
that is aligned to other GLVs:Client
andConnection
submit()
methods return aResultSet
instanceDriverRemoteConnection
submissions returns an instance ofRemoteTraversal
.This is a large-ish refactor but it doesn't represent a breaking change for the user.
Additionally, I've identified an issue when we introduced script submission support in gremlin-javascript (my bad!): We exposed a property named
traversers
(see previous code examples). I've maintained that property and marked it as deprecated, to be removed in 3.4, and updated all code examples to stop referencing to it.