[
https://issues.apache.org/jira/browse/GIRAPH-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144735#comment-13144735
]
Avery Ching commented on GIRAPH-47:
-----------------------------------
I agree with the proxy approach of WorkerContext so that a user can access a
subset of the graph state methods without directly accessing graph state. You
don't want the user to for instance "setGraphMapper".
> 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
