Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Received-SPF: pass (athena.apache.org: domain of janlugt@gmail.com designates
 209.85.161.180 as permitted sender)
MIME-Version: 1.0
Date: Thu, 14 Jun 2012 14:37:12 -0700
Message-ID: 
 <CAMOYj4CLsEMEHRR_G2h1_02wU-v0+ENqeoRmy1k2_yr3iOA=eg@mail.gmail.com>
Subject: Aggregators in a separate package
From: Jan van der Lugt <janlugt@gmail.com>
To: dev@giraph.apache.org
Content-Type: multipart/alternative; boundary=bcaec5396694aea91c04c27580f9

--bcaec5396694aea91c04c27580f9
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

A few weeks ago I filed jira
GIRAPH-192<https://issues.apache.org/jira/browse/GIRAPH-192>which
requests that several default aggregators are moved to a separate
package. In this way, they can be reused by different components. Four
aggregators exist in the examples package, but since aggregators are highly
reusable (as opposed to combiners), it makes sense to provide users with a
default set. Please let me know what you think of this proposal. I also
adjusted several classes so they use the aggregators in the aggregators
packages instead of the examples package and removed those four aggregators
there.

- Jan

--bcaec5396694aea91c04c27580f9--