[
https://issues.apache.org/jira/browse/HAMA-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863014#comment-13863014
]
Edward J. Yoon commented on HAMA-838:
-------------------------------------
I think you can handle them after calling setup() or compute() method in
GraphJobRunner, instead of access directly from vertex. But, certainly it will
have some overhead. Please ignore my suggestion.
However, we have to get rid of old interface 'setAggregatorClass'.
> Add custom aggregators
> ----------------------
>
> Key: HAMA-838
> URL: https://issues.apache.org/jira/browse/HAMA-838
> Project: Hama
> Issue Type: Improvement
> Components: graph
> Affects Versions: 0.6.3
> Reporter: Anastasis Andronidis
> Assignee: Anastasis Andronidis
> Labels: features, patch
> Fix For: 0.7.0
>
> Attachments: HAMA-838.patch
>
>
> This is a patch that adds custom aggregators.
> I also wrote an example of how you can use them.
> Implementation features:
> * Register the aggregators by name.
> * Custom aggregators are skipped when there are no messages to process
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
