Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4D0387EB2 for ; Fri, 11 Nov 2011 18:55:38 +0000 (UTC) Received: (qmail 11311 invoked by uid 500); 11 Nov 2011 18:55:37 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 11266 invoked by uid 500); 11 Nov 2011 18:55:37 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 11258 invoked by uid 99); 11 Nov 2011 18:55:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Nov 2011 18:55:37 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of todd@cloudera.com designates 209.85.161.41 as permitted sender) Received: from [209.85.161.41] (HELO mail-fx0-f41.google.com) (209.85.161.41) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Nov 2011 18:55:31 +0000 Received: by faas10 with SMTP id s10so2307759faa.14 for ; Fri, 11 Nov 2011 10:55:11 -0800 (PST) Received: by 10.152.104.206 with SMTP id gg14mr7510672lab.41.1321037711057; Fri, 11 Nov 2011 10:55:11 -0800 (PST) MIME-Version: 1.0 Received: by 10.152.38.39 with HTTP; Fri, 11 Nov 2011 10:54:50 -0800 (PST) In-Reply-To: References: From: Todd Lipcon Date: Fri, 11 Nov 2011 10:54:50 -0800 Message-ID: Subject: Re: HBase .92 maven artifacts compiled against different releases of Hadoop To: dev@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Fri, Nov 11, 2011 at 10:45 AM, Eric Yang wrote: > I recommend that one HBase release should be certified for one major rele= ase of Hadoop to reduce risk. =A0Perhaps when public Hadoop API are rock so= lid, then it will become feasible to have a version of HBase that work acro= ss multiple version of Hadoop. IMO this is entirely untenable. Different users upgrade HDFS at different rates - soon a lot of people will start to use 0.23 whereas many people will be running 0.20 for years to come. New versions of HBase need to be able to run against both (perhaps with some features or improvements only available on the latest). > > In proposed HBase structure layout change (HBASE-4337), the packaging pro= cess excludes inclusion of Hadoop jar file, and pick up from constructed cl= ass path. =A0In the effort of ensuring Hadoop related technology can work t= ogether in integrated fashion (File system layout change in HADOOP-6255). = =A0This is the starting point to ensure that Hadoop can be swap out with a = different major version for test. =A0Once the proposed structure is adopted= , HBase community can setup integration test for HBase with multiple Hadoop= major release. I don't think the file layout is the major barrier here... the barrier is people actually helping to write integration tests, and working to fix bugs as they're found. For example, would very much appreciate anyone's help to get this build green: https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-23/ -Todd --=20 Todd Lipcon Software Engineer, Cloudera