Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of jon@cloudera.com designates
 209.85.212.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALte62zF1=i+KNsimCsL-ah0N975PSfxx5+6J1zg4gYdSY9+UQ@mail.gmail.com>
References: 
 <CAAha9a1MSsyY9HRh+e6FNmx8bMVKyFuKtABD1mqzkPA1BCx6fw@mail.gmail.com>
 <CALte62zF1=i+KNsimCsL-ah0N975PSfxx5+6J1zg4gYdSY9+UQ@mail.gmail.com>
From: Jonathan Hsieh <jon@cloudera.com>
Date: Thu, 11 Apr 2013 09:45:21 -0700
Message-ID: 
 <CAAha9a10He2s4wjjSdrWh8qvm242hVP4MPya6LBdyU_RZxQCUA@mail.gmail.com>
Subject: Re: trunk on hadoop2 fixes.
To: dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=089e0112c63a5a92e404da188423

--089e0112c63a5a92e404da188423
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Apr 11, 2013 at 9:39 AM, Ted Yu <yuzhihong@gmail.com> wrote:

> Jon:
> Thanks for the headsup.
>
> Do you know that you can trigger hadoop QA to run test suite against hadoop
> 2.0 profile ?
>
> Take a look at:
>
> https://issues.apache.org/jira/secure/attachment/12575537/7904-v9-hadoop-2.0.txt
>
> Hadoop QA depends on seeing the line below in patch:
>
> hadoop.profile=2.0
>
> Neat trick. We should document this!


> You also need some changes to the pom.xml files.
>
> I want to know your strategy w.r.t. re-verifying the fixes when 2.0.4-alpha
> comes out.
> 2.0.4-alpha RC0 was cut two days ago. RC1 should come by weekend.
>
>
Let's get our current hbase trunk on hadoop2 green most of the time first,
then change to the new version.  This way we'll know if it was changes to
hbase or changes to hadoop that cause any problems that may occur.

Jon.

-- 
// Jonathan Hsieh (shay)
// Software Engineer, Cloudera
// jon@cloudera.com

--089e0112c63a5a92e404da188423--