hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Hsieh <...@cloudera.com>
Subject Re: [poll] Does anyone run or test against hadoop 0.21, 0.22, 0.23 under HBase 0.92.0+/0.94.0?
Date Thu, 19 Jul 2012 01:09:52 GMT
On Wed, Jul 18, 2012 at 5:35 PM, Stack <stack@duboce.net> wrote:

> On Thu, Jul 19, 2012 at 2:23 AM, Jonathan Hsieh <jon@cloudera.com> wrote:
> > I don't think this affects the decision you refer to. I'm not trying to
> age
> > off older versions -- I'm trying find out from this discussion which
> > "newer" versions we should have HBase work/compile against, and if we can
> > just say 1.x and 2.x and not include the 0.21, 0.22, and now 0.23
> branches.
> >
> When you say HBase 0.92/0.94 above, do you mean the next releases from
> the 0.92 and 0.94 branches (0.92.2 and 0.94.2?) would be tested
> against hadoop 1.x and 2.x only (If the result of this discussion is a
> decision that hadoop 1.0 and 2.0 are all we support)?
> I'd +1 that.  I believe the decision regarding hadoop 1.0 as the min
version in 0.96 really means that we could remove shim code currently
present to support the older 0.20-append branch then (hflush vs hsync,
etc).  The fact that our pom doesn't contain the 0.20-append branch on
0.92+ basically says to me that we aren't really testing against that at
all these days.

Today we only really run unit tests on hadoop 1.0 -- we have a hadoop 23
compile check that is done and if that build fails on jenkins no alarms are
raised (that said, the builds against 1.0.0 are better but still in pretty
rough shape).  Once we fix the last of the hadoop 2.0 unit tests
uptream I'd like to turn on the hudson builds to build and test trunk
against hadoop 2.0. As it stands today, trunk needs HBASE-5876 -- which
needs to be renamed to be hadoop 2.0; 0.94 would needs
+HBASE-5966,HBASE-5985 which are already on trunk, and 0.92 need 5966, 5985
and two I believe 2 others but does not need HBASE-5876.


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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message