I'm very sorry for the spam, the new umbrella is: https://issues.apache.org/jira/browse/HAMA-670
I would be very very glad if someone helps me with the maven scripts, I tried for an hour and it makes me really crazy :D 2012/11/12 Thomas Jungblut <[email protected]> > Yea will do. My new laptop arrived so I'd be working on installing stuff > on that now so I can phrase some jiras. > > > 2012/11/12 Suraj Menon <[email protected]> > >> Thanks Thomas, we have a start. If possible, please create a list of tasks >> to be completed under an umberella JIRA issue. This way we get a >> visibility >> into the measure of work to be done as well as progress on the issue. New >> developers can start helping you on some newbie issues that you may find >> for them :) >> >> -Suraj >> >> >> On Mon, Nov 12, 2012 at 4:44 AM, Thomas Jungblut >> <[email protected]>wrote: >> >> > FYI I will checkin a few changes: >> > - update to hadoop 2.0.2 >> > - make changes to maven scripts so Hama can be build with an arbitrary >> > version of HDFS >> > - introduce new configuration key "bsp.framework.name" which maps to >> the >> > values: "local,classic,yarn" >> > >> > The least change will change core's BSPJob, so the client can be >> overloaded >> > via a static mapping of value->classname. (e.G. local->LocalBSPRunner, >> > classic->BSPMaster and a new implementation of the JobSubmissionProtocol >> > for YARN). >> > >> > For each successive weeks I will change a part of the YARN module. I >> start >> > off by cleaning up. Following steps are: >> > >> > - Integrate the services, messaging/synchronization/scheduler >> > - Integrate counters to YARN >> > - Share the same launch code of container/task jvms >> > - Fault tolerance must also be included (if not already done by the >> > scheduler) >> > >> > Some help would be nice, if anyone can spare some time ;) >> > Thanks! >> > >> > >
