[
https://issues.apache.org/jira/browse/HAMA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anastasis Andronidis updated HAMA-767:
--------------------------------------
Attachment: HAMA-767-v3.patch
Hello, I made some heavy modifications on doAggregationUpdates(). I created a
new interface for a new type of class (PeerAggregator) that is acting like a
vertex aggregator but it has access in GraphJobRunner. I moved every logic that
applies on globalUpdateCounts inside FinishPeerAggregator. I also used the same
approach to solve the problem with vertex counting (see
CountVerticesPeerAggregator). All tests are passing, I tried to change nothing
from the workflow, but unfortunately I couldn't skip the sync for
globalUpdateCounts as it was before (we are doing 2 supersteps for 1 iteration
due to aggregators).
I still have lots to do, I just want to know if you like this approach.
> [GSoC 2013] Vertex addition and removal
> ---------------------------------------
>
> Key: HAMA-767
> URL: https://issues.apache.org/jira/browse/HAMA-767
> Project: Hama
> Issue Type: New Feature
> Components: examples, graph
> Affects Versions: 0.6.1
> Reporter: Anastasis Andronidis
> Assignee: Anastasis Andronidis
> Labels: dynamic, graph, gsoc, gsoc2013, mentoring
> Fix For: 0.6.3
>
> Attachments: HAMA-767-addAndRemove-v1.patch,
> HAMA-767-addition-v1.patch, HAMA-767-examplesAndTests-v1.patch,
> HAMA-767-v2.patch, HAMA-767-v3.patch
>
>
> Implement addVertex and removeVertex methods for incremental graph support on
> Graph API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
