[
https://issues.apache.org/jira/browse/GIRAPH-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150283#comment-13150283
]
Arun Suresh commented on GIRAPH-10:
-----------------------------------
Avery, I am assuming that a Vertex implemented by the user would have to
implement this interface if he requires his Aggregates to be persisted.. rite ?
Firstly, I feel that Aggregrators MUST be persisted at the end of each
superstep if the Vertex has implemented AggregatorWriter.
Secondly, the problem with exposing it as an interface I guess is.. Assume we
have a default AggregateWriter, how would the user include the default behavior
in his custom vertex ?
I guess a better approach would be to let the user specify the AggregaterWriter
class in the Giraph JobConf and pass an instance of the class to methods in the
BspServiceWorker class like [~cmartella] mentioned in his comment.
With respect to writing Aggregators by type.. do you mean persisting a
Map<AggregatorType, List<Entry<String, Aggregator>>> for each job ?
> 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
