[jira] [Commented] (TINKERPOP3-575) Consider implementing a RemoteGraph

["Matthias Broecheler (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TINKERPOP3-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744342#comment-14744342 ] 

Matthias Broecheler commented on TINKERPOP3-575:
------------------------------------------------

RemoteGraph would be an extremely useful tool to have when playing with OLTP+OLAP integration in particular TP3 implementations. In most such cases, you would want to execute within an OLAP context and then identify parts of a traversal that are best executed OLTP-style. Since you don't want to open an embedded OLTP graph database to the same graph source data within an OLAP context, RemoteGraph would be a handy tool to send those traversals to another machine or process to execute the traversal there.

> Consider implementing a RemoteGraph
> -----------------------------------
>
>                 Key: TINKERPOP3-575
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-575
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.0.1-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)