Re: Hadoop testing project [Was: [VOTE] Abandon mrunit MapReduce contrib]

2011-02-15 Thread Mattmann, Chris A (388J)
Sounds good to me, Cos. I'm fine to help/mentor with either one that ends up standing when the dust clears :) Cheers, Chris On Feb 15, 2011, at 1:58 PM, Konstantin Boudnik wrote: > While MrUnit discussion draws to its natural conclusion I would like > to bring up another point which might be we

Re: Hadoop testing project [Was: [VOTE] Abandon mrunit MapReduce contrib]

2011-02-15 Thread Eric Sammer
I think this is a good idea. The only thing I think is that it may make sense to split such an effort into two components: one for the testing of Hadoop and the projects themselves and one to test end user applications and libraries. Performance testing tools like YCSB are probably more in the form

Re: Hadoop testing project [Was: [VOTE] Abandon mrunit MapReduce contrib]

2011-02-15 Thread Konstantin Boudnik
On Tue, Feb 15, 2011 at 14:15, Eric Sammer wrote: > I think this is a good idea. The only thing I think is that it may make > sense to split such an effort into two components: one for the testing of > Hadoop and the projects themselves and one to test end user applications and I expect to see ev

Re: Hadoop testing project [Was: [VOTE] Abandon mrunit MapReduce contrib]

2011-02-16 Thread Steve Loughran
On 15/02/11 21:58, Konstantin Boudnik wrote: While MrUnit discussion draws to its natural conclusion I would like to bring up another point which might be well aligned with that discussion. Patrick Hunt has brought up this idea earlier today and I believe it has to be elaborated further. A numbe

RE: Hadoop testing project [Was: [VOTE] Abandon mrunit MapReduce contrib]

2011-02-16 Thread Rottinghuis, Joep
+1 Having a coherent approach for system level testing increases confidence in the various Hadoop releases and and will reduce the effort to take any (set of ) changes from development into production. The more automated and formalized system testing, the better! Thanks, Joep __

Re: Hadoop testing project [Was: [VOTE] Abandon mrunit MapReduce contrib]

2011-02-17 Thread Aaron Kimball
Working to develop code as a client of Hadoop is a path full of landmines. The more tools we can provide to users to improve the quality of their code, the better. I think it is important, though, to draw a clear distinction between tools intended for different audiences. Talking about system testi

Re: Hadoop testing project [Was: [VOTE] Abandon mrunit MapReduce contrib]

2011-02-17 Thread Konstantin Boudnik
On Thu, Feb 17, 2011 at 11:27, Aaron Kimball wrote: > Working to develop code as a client of Hadoop is a path full of landmines. > The more tools we can provide to users to improve the quality of their code, > the better. I think it is important, though, to draw a clear distinction > between tools