Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <h2m4aa34eb71005071034ja97e2f4ckca2a016efedee897@mail.gmail.com>
References: <h2m4aa34eb71005071034ja97e2f4ckca2a016efedee897@mail.gmail.com>
From: Todd Lipcon <todd@cloudera.com>
Date: Fri, 7 May 2010 10:57:48 -0700
Message-ID: <z2i45f85f71005071057u302f5d7by2f6857d4295f248d@mail.gmail.com>
Subject: Re: Hadoop support for hbase
To: general@hadoop.apache.org
Content-Type: multipart/alternative; boundary=0016367b6be852dc9b048604cda4

--0016367b6be852dc9b048604cda4
Content-Type: text/plain; charset=ISO-8859-1

I have a few questions about this proposal:

1) Will we open new JIRAs separately for each change we want to commit, and
go through the normal review process? Currently the 20-append work has been
mostly going on under HDFS-142 for whatever reason, with ancillary issues
only for bugs that also exist in trunk.
2) Do we plan to do a release off the branch, or is it meant only as a
repository for sharing patches and a tree?
3) If we do a release, what version number would we give it and how would it
be presented on the download/release pages?

I'm certainly not against the idea, just would like to open discussion on
the above points. The other alternative as I see it is to have those working
on this branch do so somewhere like github - the advantages to that would be
(a) it provides a more open way for non-committers to contribute, which is
important since we're working closely with the HBase team on this, and (b)
it doesn't add confusion to the main Hadoop jira and download pages. The
disadvantage of course is that it fragments the code repository and we can't
really do a release as easily.

Thanks
-Todd

On Fri, May 7, 2010 at 10:34 AM, Dhruba Borthakur <dhruba@gmail.com> wrote:

> Hi folks,
>
> I would like to open a discussion on how we can make HBase work well with a
> supported/released version of Hadoop. HBase currently ships with a hadoop
> jar and that hadoop jar is from hadoop 0.20 + a set of ten/twenty patches.
> Most of these patches are focussed on HDFS append support in hadoop 0.20.
> These cannot be ported back to the 0.20 branch without affecting stability
> of the hadoop 0.20 branch. On the other hand, it is premature for hbase
> deployments to use hadoop 0.21 because hadoop 0.21 is still under testing
> and will take some time to stabilize.
>
> My proposal is to create a new branch off the hadoop 0.20 branch and name
> it branch-0.20-hbase. It will have support for append/sync and will be API
> compatible with the hadoop 0.20 branch. However, this branch will be marked
> "experimental" and API compatibility is subject to change. This branch will
> contain all of hdfs/mapreduce/core.
>
> If the community likes this idea, I will volunteer myself to be the release
> manager for this new branch and will propose a formal vote.
>
> comments/feedback/questions are most welcome.
> dhruba
>
>
> --
> Connect to me at http://www.facebook.com/dhruba
>


-- 
Todd Lipcon
Software Engineer, Cloudera

--0016367b6be852dc9b048604cda4--