You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2016/02/09 20:13:18 UTC
[jira] [Commented] (TINKERPOP-575) Consider implementing a
RemoteGraph
[ https://issues.apache.org/jira/browse/TINKERPOP-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139439#comment-15139439 ]
Marko A. Rodriguez commented on TINKERPOP-575:
----------------------------------------------
This is ready to be implemented when TINKERPOP-971 is merged. Should be fun.
> Consider implementing a RemoteGraph
> -----------------------------------
>
> Key: TINKERPOP-575
> URL: https://issues.apache.org/jira/browse/TINKERPOP-575
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.0.2-incubating
> Reporter: Bryn Cooke
>
> 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)