I'm putting the answer in line.
On Thu, Jan 19, 2012 at 6:22 PM, Avery Ching wrote:
> Not sure if Semih is on the giraph-dev list. Forwarding the question to
> him.
>
> Avery
>
> P.S. Interesting idea if I understand correctly, attaching the compute
> functionality to an aggregator that the ma
Not sure if Semih is on the giraph-dev list. Forwarding the question to
him.
Avery
P.S. Interesting idea if I understand correctly, attaching the compute
functionality to an aggregator that the master will run between supersteps?
On 1/19/12 1:20 PM, Claudio Martella wrote:
Hi Semih,
inte
[
https://issues.apache.org/jira/browse/GIRAPH-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189574#comment-13189574
]
Avery Ching commented on GIRAPH-127:
I think this functionality is very useful and wou
Hi Semih,
interesting email. I'm probably not getting your technique right, but
why wouldn't it be possible to compute the master.compute() inside of
an aggregator?
Not only it *should* be possible, but as aggregators are computed both
on workers AND on the master, you should have a faster comput
Extending the API with a master.compute() function.
---
Key: GIRAPH-127
URL: https://issues.apache.org/jira/browse/GIRAPH-127
Project: Giraph
Issue Type: New Feature
Components: bsp,