hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon" <edwardy...@apache.org>
Subject Re: Setup Computation Cleanup
Date Fri, 07 Oct 2011 10:18:33 GMT
+1

2011/10/7 ChiaHung Lin <chl501@nuk.edu.tw>:
> +1
>
> That looks what we need because we also have procedure to create/ clean e.g. temp directory
IIRC.
>
> -----Original message-----
> From:Tommaso Teofili <tommaso.teofili@gmail.com>
> To:hama-dev@incubator.apache.org
> Date:Fri, 7 Oct 2011 10:39:41 +0200
> Subject:Re: Setup Computation Cleanup
>
> big +1 from me :)
> Tommaso
>
> 2011/10/7 Thomas Jungblut <thomas.jungblut@googlemail.com>
>
>> Hi all,
>>
>> like you may know I want to have a bit more structure (in terms of
>> intuition) in our API to the user.
>> 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.
>> So users could be able to execute initial message sending in the setup
>> method, as well as synchronizing.
>>
>> What do you think?
>>
>> --
>> Thomas Jungblut
>> Berlin <thomas.jungblut@gmail.com>
>>
>
>
> --
> ChiaHung Lin
> Department of Information Management
> National University of Kaohsiung
> Taiwan
>



-- 
Best Regards, Edward J. Yoon
@eddieyoon

Mime
View raw message