Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 15445 invoked from network); 5 Jul 2010 18:22:37 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Jul 2010 18:22:37 -0000 Received: (qmail 13544 invoked by uid 500); 5 Jul 2010 18:22:36 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 13486 invoked by uid 500); 5 Jul 2010 18:22:35 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 13478 invoked by uid 99); 5 Jul 2010 18:22:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Jul 2010 18:22:34 +0000 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.214.169] (HELO mail-iw0-f169.google.com) (209.85.214.169) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Jul 2010 18:22:27 +0000 Received: by iwn2 with SMTP id 2so4782961iwn.14 for ; Mon, 05 Jul 2010 11:21:06 -0700 (PDT) Received: by 10.231.155.3 with SMTP id q3mr3252748ibw.20.1278354066310; Mon, 05 Jul 2010 11:21:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.161.72 with HTTP; Mon, 5 Jul 2010 11:20:46 -0700 (PDT) In-Reply-To: References: <4C2C8D35.3080707@kalooga.com> <4C2CDEFD.7040001@kalooga.com> <4C2DA25E.2000006@kalooga.com> From: Todd Lipcon Date: Mon, 5 Jul 2010 11:20:46 -0700 Message-ID: Subject: Re: About HDFS-630 and hbase 0.20.5 To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=00504501423a0506f5048aa80021 X-Virus-Checked: Checked by ClamAV on apache.org --00504501423a0506f5048aa80021 Content-Type: text/plain; charset=ISO-8859-1 Hi, Yep, it looks like it's a bug in our releasenote generation script. Sorry about that - the CHANGES.txt files are the definitive source for what's in there. We generate the release notes from there, but there's an indirection in between and it looks like a bug caused us to drop that JIRA from the notes. To be clear, HDFS-630 is included in 0.20.1+169.89 (the latest CDH2, ie CDH2u1) as well as both betas of CDH3. -Todd On Fri, Jul 2, 2010 at 9:54 AM, Jean-Daniel Cryans wrote: > Maybe their release notes are outdated or something, but it is there. > See http://archive.cloudera.com/cdh/2/hadoop-0.20.1+169.89.CHANGES.txt > > J-D > > On Fri, Jul 2, 2010 at 1:25 AM, Ferdy wrote: > > Cool thanks. These cloudera distributions certainly look promising. > > > > One final note, I could not find the HDFS-630 patch in the CDH2. I don't > > mean to nitpick but I'm still left wondering if I should include it or > not. > > > > Do you guys patch the CDH2 with HDFS-630 or what? Or would you say this > > patch is not so important after all? > > > > Ferdy > > > > This seems to be the newest CDH2 release: > > http://archive.cloudera.com/cdh/2/hadoop-0.20.1+169.89.releasenotes.html > > > > Jean-Daniel Cryans wrote: > >> > >> Yes, and to deploy the cloudera release on your cluster :) > >> > >> J-D > >> > >> On Thu, Jul 1, 2010 at 11:31 AM, Ferdy > wrote: > >> > >>> > >>> Allright so I will use a cloudera release. If I understand correctly, > >>> this > >>> includes simply replacing the Hadoop jar in the hbase/lib folder with > the > >>> cloudera hadoop core jar? > >>> > >>> Ferdy. > >>> > >>> On 07/01/2010 08:23 PM, Jean-Daniel Cryans wrote: > >>> > >>>> > >>>> On Thu, Jul 1, 2010 at 5:42 AM, Ferdy > wrote: > >>>> > >>>> > >>>>> > >>>>> > >>>>> > http://hbase.apache.org/docs/r0.20.5/api/overview-summary.html#overview_description > >>>>> > >>>>> Here is states that it is recommended to use HDFS-630 patch for > Hadoop. > >>>>> So, > >>>>> why does the hbase 0.20.5 contains a stock hadoop 0.20.2 jar? (Hadoop > >>>>> 0.20.2 > >>>>> does not have HDFS-630 fixed). > >>>>> > >>>>> > >>>> > >>>> What Ted said, and also we cannot ship with a patched jar simply > >>>> because it's not a client side-only change. If we did, it would mean > >>>> that our release of HBase wouldn't be compatible with any official > >>>> Apache Hadoop release. > >>>> > >>>> I agree with Todd, you can simply use CDH2. This is what we do on all > >>>> our clusters at StumbleUpon. > >>>> > >>>> J-D > >>>> > >>>> > > > -- Todd Lipcon Software Engineer, Cloudera --00504501423a0506f5048aa80021--