giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maja Kabiljo (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GIRAPH-939) Reduce/broadcast API
Date Fri, 10 Oct 2014 19:59:34 GMT

     [ https://issues.apache.org/jira/browse/GIRAPH-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Maja Kabiljo resolved GIRAPH-939.
---------------------------------
    Resolution: Fixed

> Reduce/broadcast API
> --------------------
>
>                 Key: GIRAPH-939
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-939
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Igor Kabiljo
>
> Add reduce and broadcast API.
> Current aggregator API has multiple issues:
> - no matter whether aggregated values are needed on workers, they are distributed to
them
> - there is no way to register aggregator for a single superstep
> - in order for master to send data to workers, it needs to go through an aggregator -
even though it can only be Writable
> - value to be aggregated and result of aggregation need to be of the same type
> - logic of how to do aggregation is combined with how Aggregator is kept (i.e. aggregate(valueToAggregate),
instead of aggregate(currentAggregatedValue, valueToAggregate)), and so every aggregator needs
to extend BasicAggregator, but that still limits what can be done.
> reduce/broadcast is the simplest comprehensive API for what it does, and Aggregator API
can be built on top of it



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message