hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-838) Add custom aggregators
Date Mon, 06 Jan 2014 12:00:55 GMT

    [ https://issues.apache.org/jira/browse/HAMA-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862936#comment-13862936
] 

Edward J. Yoon commented on HAMA-838:
-------------------------------------

IMO, the registerAggregator() should be added to VertexInterface, not GraphJob. Then, user
can register new aggregator within setup() and compute() method in Vertex program. And, I
think we have to get rid of old interface 'setAggregatorClass'.

Additionally, if user can get Aggregators from a finished job as follows:

{code}
GraphJob exampleJob = new GraphJob();
....
Aggregators aggregators = exampleJob.getAggregators();
{code}

This will really cool.

> 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)

Mime
View raw message