[
https://issues.apache.org/jira/browse/HAMA-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266860#comment-13266860
]
Thomas Jungblut commented on HAMA-567:
--------------------------------------
Sorry, but I dislike this Object usage. That's what generics are for. I
currently have no clue about how to make it better, but maybe multiple Maps
that are generic for each object added.
We can delegate contains, "isObjectPresentFor" is a bit too verbose, the same
with get as "getSavedObject" and save can be put.
No matter what, we have to extract some interface for that (I prefer generics)
and add implementation for off-heap caching solutions like direct memory. These
things are very GC heavy and it is better to not store that on the heap
directly.
bq. Shall we add this in 0.5 release
Let's put that into 6.0 when we try to add the remote memory things.
> 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
