Add Support For Remote Graph Traversals

[karthicks]

One of the concerns that came out of the DISCUSS thread for the pull request for TINKERPOP-1750 was that the gremlin-objects library might run into issues when dealing with a remote traversal, specifically one generated using the graph.traversal().withRemote(...) option. To quote Stephen Mallette, the issue is that "You get back a "reference" vertex which only has
the id and label - no properties."

Given that gremlin-objects terminates the GraphTraversal using either a next or a toBulkSet action, it may be possible that the properties in the resulting vertex does have the properties we need, in which case no changes would be required. If not, then we may need to explicitly ask for each property using the properties or values step, before doing the next or toBulkSet step.

In any case, a test case that addresses this use case is needed, and this issue tracks that effort.

[lindamthomas07]

Any updates on this one?

[arvind-das]

seems like this is inactive since long. Remote connection is important , currently it could be achieved by clustered client submitting queries. Existing solutions of embedded force to scale with client app.
These guys started but have a big issue for autogenerated id saving.
Microsoft spring data gremlin