[
https://issues.apache.org/jira/browse/HAMA-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221861#comment-13221861
]
ChiaHung Lin commented on HAMA-503:
-----------------------------------
That's a minor issue, not a big problem. Just thought that may avoid confusing
users with the same function name.
By the way, how can we implement k-means clusters with this new interface?
k-means algorithm dynamically constructs supersteps
{code}
... bsp() ...{
while(isConverged()){
assignmentStep();
updateStep();
}// end while
}// end bsp
{code}
So it seems to me allowing user to dynamic specify supersteps is still
required. With the current patch, users need to know how many supersteps are
going to be processed before job is executed. Or is there alternative way to
work around this issue?
> 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
> Assignee: Thomas Jungblut
> Fix For: 0.5.0
>
> Attachments: HAMA-503.patch
>
>
> 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
