[
https://issues.apache.org/jira/browse/HAMA-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200490#comment-13200490
]
Thomas Jungblut commented on HAMA-503:
--------------------------------------
Two ideas for a computation "class".
- Use methods and annotations like:
@Superstep(1)
@Superstep(2)
It will execute in that order. Like JUnit we can also loop through the method
names, but I don't think this is much more convenient.
- Generic types for the messages
The method which does execute the first superstep get's let's say <Integer,
Double,?, ?> as input and ? as output, let's say String. (these should be
Writable then..) -> <Integer, Double, String, String>
The second superstep method has to get <String, String, Integer, Double>
assuming that there is no other superstep defined.
I currently don't know a way how to archieve this without defining several
classes. But I will have a deeper look and hack a prototype over the next week.
> Chainable computations for tault tolerance
> ------------------------------------------
>
> Key: HAMA-503
> URL: https://issues.apache.org/jira/browse/HAMA-503
> Project: Hama
> Issue Type: Sub-task
> Components: bsp
> Affects Versions: 0.4.0
> Reporter: Thomas Jungblut
> Fix For: 0.5.0
>
>
> refactor bsp() in allowing checkpointed messages to be recovered.
> ChiaHung Lin had a fancy idea in chaining superstep class to make the whole
> recovering more convenient and less error prone, or at least possible.
> A user does not define a BSP anymore, instead he defines a single superstep
> inside of a computation class. A user is able to chain these in a specific
> ordering. After each of this computation the framework calls sync() and
> exchanges the messages.
--
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
