>From Bigtop perspective, Hadoop  2.0.4.1 is unblocked with regards to a Sqoop 
>2 blocker, and the voting can be started.

Anatoli

---------- Forwarded message ----------
From: Konstantin Boudnik <c...@apache.org>
Date: Mon, May 20, 2013 at 9:03 PM
Subject: Re: Bugfix release 2.0.4.1
To: common-dev@hadoop.apache.org


The build is over, all unit tests have passed.
Roman, the 2.0.4.1 tarballs are available from
https://builds.apache.org/job/ Hadoop-branch-2.0.4/47/

For Bigtop to use as the base.
  Cos

On Mon, May 20, 2013 at 12:15PM, Konstantin Boudnik wrote:
> I have ran the full set of unit tests on the patched version and I see 3
> failures in HDFS HA stress tests, which are clearly not related to fix in
> question. I will commit it shortly.
>
> Cos
>
> On Thu, May 16, 2013 at 12:03AM, Roman Shaposhnik wrote:
> > On Wed, May 15, 2013 at 11:09 PM, Vinod Kumar Vavilapalli
> > <vino...@hortonworks.com> wrote:
> > >
> > > It's a little dirty, but Mark and Jarek (presumably from BigTop) ran a 
> > > patched version with my change at MAPREDUCE-5240.
> >
> > I've just updated the patch to apply cleanly on branch-2.0.4 (had to 
> > refactor
> > quite a bit of unit tests). Hopefully Cos can apply it tomorrow and we
> > can start testing Bigtop.
> >
> > > Otherwise we may end up creating lots of bug-fix releases.
> >
> > Agreed. The point of 2.0.4.1 is to unblock Bigtop 0.6.0 release. We're
> > trying to come with stable base line for Hadoop 2.0.x where
> > all the downstream components will be running smoothly.
> >
> > At this point a MAPREDUCE-5240 is the only thing holding us
> > up, but once we start our own round of testing other issues
> > could pop up. We shall see how it goes.
> >
> > Thanks,
> > Roman.  

Reply via email to