[
https://issues.apache.org/jira/browse/TINKERPOP-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201330#comment-15201330
]
ASF GitHub Bot commented on TINKERPOP-575:
------------------------------------------
Github user spmallette commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/269#issuecomment-198311155
@mpollmeier that was a nice bug find. i never unpackaged the zip and my
assembly files had a bug in them. the `scripts` directory wasn't being included
so the graph couldn't get initialized with data which so you were executing
your remotes against an empty graph and getting no results. Should work for
you now if you try again. Reviewing the distributions now to be sure nothing
else is amiss.
> Implement RemoteGraph
> ---------------------
>
> Key: TINKERPOP-575
> URL: https://issues.apache.org/jira/browse/TINKERPOP-575
> Project: TinkerPop
> Issue Type: Improvement
> Components: driver, process, server
> Affects Versions: 3.0.2-incubating
> Reporter: Bryn Cooke
> Assignee: stephen mallette
> Fix For: 3.2.0-incubating
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
