giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claudio Martella (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-47) Export Worker's Context/State to vertices through pre/post/Application/Superstep
Date Sat, 05 Nov 2011 12:16:51 GMT

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

Claudio Martella commented on GIRAPH-47:
----------------------------------------

I'm actually kind of a big fan of passing the GraphState to WorkerContext. I've already changed
the API accordingly and noticed it's often very handy. Checkout what pre/post/superstep/application
code does in the examples and benchmarks, it often relies on things like the current superstep,
the number of vertices etc, all things that are easily accessible by GraphState. Maybe we
might want to hide some of them by making WorkerContext an abstract and proxy them? In this
case we might want to proxy the aggregatorUsage code as well. Wouldn't this go more towards
the direction Jakob was thinking? All this could then be simply removed from BasicVertex.

Currently WorkerContext cannot implement Aggregator methods as it doesn't have a handle to
AggregatorUsage, or am I missing something?
                
> Export Worker's Context/State to vertices through pre/post/Application/Superstep
> --------------------------------------------------------------------------------
>
>                 Key: GIRAPH-47
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-47
>             Project: Giraph
>          Issue Type: Improvement
>          Components: graph
>    Affects Versions: 0.70.0
>            Reporter: Claudio Martella
>            Assignee: Claudio Martella
>         Attachments: GIRAPH-47.diff
>
>
> It would be quite useful for vertices to reach some worker-related information stored
i.e. in the GraphState class.
> This information could be exported as a parameter to pre/post/Application/Superstep like
this:
> public void preApplication(Configurable workerObject);
> public void postApplication(Configurable workerObject);
> public void preSuperstep(Configurable workerObject);
> public void postSuperstep(Configurable workerObject);
> public Configurable getWorkerObject();
> Another possibility is to add a Context inner class to BasicVertex to store this information.

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