incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Jungblut (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-448) Restructure BSP API
Date Mon, 10 Oct 2011 12:13:29 GMT

    [ https://issues.apache.org/jira/browse/HAMA-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124017#comment-13124017
] 

Thomas Jungblut commented on HAMA-448:
--------------------------------------

Sure, let's try this out.
                
> 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
>
>         Attachments: HAMA-448_v1.patch
>
>
> 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

        

Mime
View raw message