Claudio Martella commented on GIRAPH-47:

Sounds very reasonable. We would then remove those methods from BasicVertex API 
I guess. I'll work on this. Unfortunately I can't test it on my application as 
it's blocked by GIRAPH-36, so I'll think about a toy-example to test this out.

One question: what would be this Configurable workerObject you'd pass to the 
WorkerContext implementation?
> 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
> 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: 
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to