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 2015/11/23 18:13:11 UTC

[jira] [Updated] (TINKERPOP3-383) TraversalVertexProgram Message Sending

     [ https://issues.apache.org/jira/browse/TINKERPOP3-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marko A. Rodriguez updated TINKERPOP3-383:
------------------------------------------
    Assignee:     (was: Marko A. Rodriguez)

> TraversalVertexProgram Message Sending
> --------------------------------------
>
>                 Key: TINKERPOP3-383
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-383
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.0.2-incubating
>            Reporter: Matthias Broecheler
>
> Should use LocalMessageScope to access edges rather than assuming it has full access to the star-graph around a vertex which may not be the case for partitioned vertices.
> For instance, g.E will execute v.outE on all vertices. Rather, it should send messages on inE.
> In general, TraversalVertexProgram should only send global messages when it absolutely has to (e.g. jumping) in order to be optimizable by the executing GraphComputer which currently cannot make any assumption about the execution and always has to retrieve the entire star-graph which may be inefficient.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)