You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Thomas Jungblut (Assigned) (JIRA)" <ji...@apache.org> on 2011/10/10 10:32:30 UTC
[jira] [Assigned] (HAMA-448) Restructure BSP API
[ https://issues.apache.org/jira/browse/HAMA-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Jungblut reassigned HAMA-448:
------------------------------------
Assignee: Thomas Jungblut
> Restructure BSP API
> -------------------
>
> Key: HAMA-448
> URL: https://issues.apache.org/jira/browse/HAMA-448
> Project: Hama
> Issue Type: Improvement
> Reporter: Thomas Jungblut
> Assignee: Thomas Jungblut
> Labels: bsp
> Fix For: 0.4.0
>
>
> Excerpt from the mailing list:
> I would like to add a setup(BSPPeer peer) and a cleanup(BSPPeer peer) method to our abstract BSP class.
> In addition I want to implement the setConfiguration and getConfiguration in our abstract BSP class, add a Configuration field, and set them to deprecated. (maybe we can remove them in our 5.0 release).
> To retrieve the job's configuration, the user should use peer.getConfiguration().
> Similar to the Hadoop flow, we are executing setup->bsp->cleanup.
> Maybe we can refactor our examples to match this new possibility.
--
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