[
https://issues.apache.org/jira/browse/TINKERPOP-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez closed TINKERPOP-1132.
-----------------------------------------
Resolution: Invalid
This can't be done for either of the GraphComputers we support. Giraph doesn't
allow it. SparkGraphComputer shouldn't because then failures might cause
inconsistencies. And TinkerGraphComputer is a nasty iterator
map().filter()-chain to get the messages and your can't remove(). Closing this
issue.
> Messenger.receiveMessages() Iterator should .remove().
> ------------------------------------------------------
>
> Key: TINKERPOP-1132
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1132
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.1.1-incubating
> Reporter: Marko A. Rodriguez
> Assignee: Marko A. Rodriguez
> Fix For: 3.2.0-incubating
>
>
> {code}
> public interface Messenger<M> {
> /**
> * Receive all incoming messages to the currently executing vertex.
> *
> * @return the messages for the vertex
> */
> public Iterator<M> receiveMessages();
> /**
> * The currently executing vertex can send a message with provided {@link
> MessageScope}.
> *
> * @param messageScope the message scope of the message being sent
> * @param message the message to send
> */
> public void sendMessage(final MessageScope messageScope, final M message);
> }
> {code}
> The Iterator from {{recieveMessages()}} should be drained with each
> {{.next()}}. We can't force a provider to do it (as its not testable), but we
> can do it for {{SparkGraphComptuer}}, {{GiraphGraphComputer}}, and
> {{TinkerGraphComputer}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
