Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of jdcryans@gmail.com designates
 74.125.83.48 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=MPXw0es361G06boqaxQv9dwEPrsmccEiqfti0PdW5IV1HoOK3IC3TILrNSKeGaqeYJ
         VSluZSmx/vzpOcRvAGowVP3nqM6DFMNz8gghB2Bk2D19g7Q85/Z1FJvVdKgXJiMrwq60
         k88vP0ygvj0IKdzgTzTXZjqI3B1ZZVZGdvLhY=
MIME-Version: 1.0
Sender: jdcryans@gmail.com
In-Reply-To: <45f85f71003181132x81d010et8987550b5647b692@mail.gmail.com>
References: <7c962aed1003181128q6dee4d5fr93cc163ba8de2bee@mail.gmail.com>
	 <45f85f71003181132x81d010et8987550b5647b692@mail.gmail.com>
Date: Thu, 18 Mar 2010 11:34:39 -0700
Message-ID: <31a243e71003181134r3fce8270pfb64ccbeca86a28b@mail.gmail.com>
Subject: Re: [MORE DISCUSSION] Moving hbase trunk (temporarily) back to hadoop
	0.20.x (from head of the hadoop 0.21 branch)
From: Jean-Daniel Cryans <jdcryans@apache.org>
To: hbase-dev@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I'm obviously +1

@Todd, that's the plan https://issues.apache.org/jira/browse/HBASE-2233

J-D

On Thu, Mar 18, 2010 at 11:32 AM, Todd Lipcon <todd@cloudera.com> wrote:
> +1 from me.
>
> To help out the guys who are already running on unreleased Hadoop, would =
it
> be possible to build a simple shim layer that would allow it to work with
> either? We did this in Hive and it seems to be working well (few complain=
ts
> so far)
>
> -Todd
>
> On Thu, Mar 18, 2010 at 11:28 AM, Stack <stack@duboce.net> wrote:
>
>> Unless there is objection, in the next day or so, I'd like to revert
>> the hadoop that is in hbase trunk and replace it with hadoop 0.20.2.
>> Currently hbase trunk bundles the head of the 0.21 hadoop branch and
>> will only run atop an hadoop built out of this hadoop 0.21 branch.
>>
>> Since the plan is that the next release of hbase will run on hadoop
>> 0.20.x and the major hadoop release that follows hadoop 0.20 -- 0.21
>> or 0.22, its version is still TBD -- AND given that the next major
>> hadoop release would seem to be a few months out, having our trunk
>> bundle hadoop 0.21 unnecessarily constrains where current hbase trunk
>> can run.
>>
>> Even though the bundled hadoop 0.21 has the critical hdfs-265 working
>> flush/sync feature, its looking like hard work by the fellas who are
>> on the hdfs-200, hdfs-862 and hdfs-142 patchset will likely get us
>> data durability on a (patched) hadoop 0.20.x some time soon. =A0Having
>> hbase trunk so it can work on the patched hadoop 0.20.x will help the
>> testing of the data durability effort.
>>
>> Jean-Daniel, Ryan, and I have already had a pow-wow about this and
>> think this is the way to go for now (The revert notion was originally
>> Ryans -- See HBASE-2255).
>>
>> If you've been running hbase TRUNK and an hadoop 0.21, unfortunately,
>> this means that you'll need to copy your data out of your cluster, do
>> the downgrade, and then copy your data back in. =A0If you need help with
>> this effort, give us a shout and we'll help you out.
>>
>> Thanks,
>> St.Ack
>>
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera
>