giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan van der Lugt (JIRA)" <j...@apache.org>
Subject [jira] [Created] (GIRAPH-192) Move aggregators to a seperate sub-package
Date Mon, 21 May 2012 22:39:41 GMT
Jan van der Lugt created GIRAPH-192:
---------------------------------------

             Summary: Move aggregators to a seperate sub-package
                 Key: GIRAPH-192
                 URL: https://issues.apache.org/jira/browse/GIRAPH-192
             Project: Giraph
          Issue Type: Improvement
          Components: examples
            Reporter: Jan van der Lugt
            Priority: Minor


Since aggregators will be re-used throughout many projects and algorithms, it makes sense
to implement the most common ones in a separate sub-package. This will reduce the time required
for users when they implement their projects based on Giraph, because the required aggregators
are already in place. I implemented the following ones:
for int/long/float/double: min, max, overwrite
for long/double: product, sum
for boolean: and, or, overwrite

Most of them speak for themselves, except for the overwrite one. This aggregator simply overwrites
the stored value when a new value is aggregated. This is useful when one node is in some way
a master node (for example a source node in an routing algorithm), and this node wants to
broadcast a value to all other nodes.

Attached is a patch against trunk implementing the aggregators and patching some existing
files so they use the .aggregators package instead of the .examples one.

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

        

Mime
View raw message