[jira] [Closed] (TINKERPOP3-611) Messenger.receiveMessages(no args)

["Marko A. Rodriguez (JIRA)" <ji...@apache.org>]

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

Marko A. Rodriguez closed TINKERPOP3-611.
-----------------------------------------
    Resolution: Fixed

This has been implemented. For Giraph and Spark, it was a simple fix. For {[TinkerGraphComputer}}, {{TinkerMessageBoard}} was updated with currentScope and previousScope type sets that are "flipped" on {{messageBoard.completeIteration()}}.

> Messenger.receiveMessages(no args)
> ----------------------------------
>
>                 Key: TINKERPOP3-611
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-611
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>            Reporter: Marko A. Rodriguez
>             Fix For: 3.0.0.GA
>
>
> Right now {{Messenger.recieveMessages()}} takes a {{MessageScope}} argument. This is oriented towards "message pulling systems" that require the {{MessageScope}} to know which adjacent vertices to get their messages from. For "message passing systems" this is not needed and in fact, if required, requires some sort of message tagging and non-Iterator behavior.  
> We should get rid of the {{MessageScope}} argument and "message pull systems" can simply get the {{MessageScope}}s from {{VertexProgram.getMessageScopes(iteration)}}.



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