[
https://issues.apache.org/jira/browse/HAMA-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295493#comment-13295493
]
Apurv Verma commented on HAMA-550:
----------------------------------
1) What is the benefit of declaring getSourceVertex as static?
2) Removed the empty annotations
3) TODO, I was hoping of a feature where vertex value and message type need not
be same type.
4) Done
5) Used configuration, I guess this is because static variables won't be
distributed across the cluster whereas with a conf, they will be.
6) Used streams.
BTW I have implemented it in a way that it works, but I still think
FLAG_MESSAGE_COUNTS should be kept separate from FLAG_ACTIVE_VERTEX_COUNTS. It
may happen that at some superstep all vertices have votedToHalt but they had
some information to send to other vertices in this superstep (before calling
sync at the end of this superstep) i.e there were some messages in transit.
But we can handle that case later, when we mandataroly req. such an
implementation in an algorithm.
Thanks
> Implementation of Bipartite Matching
> ------------------------------------
>
> Key: HAMA-550
> URL: https://issues.apache.org/jira/browse/HAMA-550
> Project: Hama
> Issue Type: New Feature
> Components: examples, graph
> Reporter: Edward J. Yoon
> Assignee: Apurv Verma
> Labels: examples
> Fix For: 0.5.0
>
> Attachments: HAMA-550.patch, HAMA-550.patch, HAMA-550.patch,
> tgraph.txt
>
>
> See http://markmail.org/thread/eaq7p5r2bbjoyfsa
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
