[
https://issues.apache.org/jira/browse/HAMA-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266894#comment-13266894
]
Suraj Menon commented on HAMA-567:
----------------------------------
Oops forgot to answer on the API function names. I thought put, get and
containsKey are expected behavior of a Map. But I thought the names should
explain more about this behavior for BSPPeer class which is not a map. Hence
the extra verbosity.
I am just throwing this idea out. Should we have containsKey and get take the
Class-name of the expected object to prevent ClassCastExceptions?
> BSPPeer should provide means for chaining supersteps to share data among them.
> ------------------------------------------------------------------------------
>
> Key: HAMA-567
> URL: https://issues.apache.org/jira/browse/HAMA-567
> Project: Hama
> Issue Type: Improvement
> Components: bsp core
> Affects Versions: 0.6.0
> Reporter: Suraj Menon
> Fix For: 0.6.0
>
>
> In most scenarios, a superstep would need certain values or objects that were
> computed in the previous superstep. When using the chaining Superstep design
> to implement BSP algorithms, this gets a little ugly/difficult to implement.
> BSPPeer should provide means (preferably a map<String,Object>) so that the
> next Superstep can ask for the values in previous superstep using String
> token to query the map. Also, this map could be checkpointed periodically in
> the background so that we can completely recover the state of a task after
> failure. The BSPPeer object should have a dedicated get and set function for
> updating values in the peer.
--
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
