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 2017/02/01 17:19:51 UTC

[jira] [Closed] (TINKERPOP-1208) Support for MessageScope.Subgraph in GraphComputer

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

Marko A. Rodriguez closed TINKERPOP-1208.
-----------------------------------------
    Resolution: Duplicate
      Assignee: Marko A. Rodriguez

This is being handled by the {{Partition}}/{{Partitioner}} ticket. TINKERPOP-1564. Thus, closing this duplicate.

> Support for MessageScope.Subgraph in GraphComputer
> --------------------------------------------------
>
>                 Key: TINKERPOP-1208
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1208
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.1.1-incubating
>            Reporter: Marko A. Rodriguez
>            Assignee: Marko A. Rodriguez
>
> I don't really know the best way to express this, but I think we should allow a {{VertexProgram}} to state which vertices it should process at each iteration. For most {{VertexProgram}}s only those vertices that received a message in the last iteration need to be evaluated. What is the best way to say this so that {{GraphComputer}} implementations can use it, I don't know. 
> This is all really related to {{GraphFilter}} and {{MessageScope}} as well. Basically, at every iteration, what subgraph do you need to grab to process? ... we should really tie all those concepts together nicely.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)