[TINKERPOP-575] Implement RemoteGraph

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Implemented
• Affects Version/s: 3.0.2-incubating
• Fix Version/s: 3.2.0-incubating
• Component/s: driver, process, server
• Assignee: Stephen Mallette
• Reporter: Bryn Cooke
• Created: 18/Feb/15 10:14
• Updated: 21/Mar/16 21:34
• Resolved: 18/Mar/16 13:31

Description

Consider implementing a graph that allows remote execution of portions of a gremlin query and locally executes steps that have lambda expressions.

Graph r = new RemoteGraph("192.168.0.10") //Gremlin server

r.V().has("age", 35).out().in().sideEffect(v->

{do something});

gets optimised to
r.remoteStep("g.V().has("age", 35).out().in()").sideEffect(v->{do something}

);

The remote step would be transmitted to the server for execution and the results pulled back allow the side effect to take place locally.

All remote step optimisation is done via traversal strategy.

Things to think about are:
Transactions have to span multiple requests to the server.
Strategies only work on the server side.

Issue Links

• depends upon: TINKERPOP-971 TraversalSource should be fluent like GraphComputer
• is blocked by: TINKERPOP-1202 Deserialized Traversal does not return Traversers
• is related to: TINKERPOP-1230 Serialising lambdas for RemoteGraph