[
https://issues.apache.org/jira/browse/GIRAPH-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121036#comment-13121036
]
Claudio Martella commented on GIRAPH-47:
----------------------------------------
another much easier way, at least for me, would be just to add a getContext()
inside of BasicVertex and return GraphMapper's Context. In this case I'd guess
we could also change the definition of Mapper from <Object, Object, Object,
Object>, although it should work anyway if the the object to write implements
toString() accordingly.
Or, third possibility, adding an emit(Writable key, Writable value) method to
BasicVertex that forwards to Context.write().
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
