Mailing-List: contact giraph-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: giraph-dev@incubator.apache.org
Date: Thu, 29 Sep 2011 19:49:45 +0000 (UTC)
From: "Avery Ching (Commented) (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <13351816.8824.1317325785620.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <185546435.2003.1314586657723.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (GIRAPH-10) Aggregators are not exported
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Avery Ching commented on GIRAPH-10:
-----------------------------------

This is definitely an open question here.  Here's a quick thought off the top of my head.

How about something like:

public interface AggregatorsWriter {
    void initialize(TaskAttemptContext context, int superstep) throws IOException;

    void writeAggregators(Collection<Aggregator<? extends Writable>> aggregators)
        throws IOException, InterruptedException;

    void close(TaskAttemptContext context)
        throws IOException, InterruptedException;
}

Then we could define a method that lets the user select the frequency of how frequently to write the aggregators maybe with an enum (ALL_SUPERSTEPS, LAST_SUPERSTEP...).

We could easily implement a default AggregatorsWriter that simply dumps the name and aggregator values with the registered aggregator name (maybe class name too) and then the value.toString().  And users can implement something better if they like.

Another alternative would be to support writing aggregators separately by the type, but might be a little excessive and could be done later....hopefully someone else also chimes in with some thoughts.
                
> Aggregators are not exported
> ----------------------------
>
>                 Key: GIRAPH-10
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-10
>             Project: Giraph
>          Issue Type: New Feature
>            Reporter: Avery Ching
>            Priority: Minor
>
> Currently, aggregator values cannot be saved after a Giraph job.  There should be a way to do this.

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