Return-Path: Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: (qmail 76230 invoked from network); 9 May 2010 22:06:46 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 9 May 2010 22:06:46 -0000 Received: (qmail 72598 invoked by uid 500); 9 May 2010 22:06:45 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 72522 invoked by uid 500); 9 May 2010 22:06:45 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 72514 invoked by uid 99); 9 May 2010 22:06:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 May 2010 22:06:45 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of saint.ack@gmail.com designates 209.85.221.172 as permitted sender) Received: from [209.85.221.172] (HELO mail-qy0-f172.google.com) (209.85.221.172) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 May 2010 22:06:37 +0000 Received: by qyk2 with SMTP id 2so5517009qyk.20 for ; Sun, 09 May 2010 15:06:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=ayxvp4+g46sET8Ws7AaMdfq1L4sePdXs4Btw48oRHjU=; b=h/D1t1EI302QzIwYs79p8MxLDufuYGHJzCMG92BCWBAszppQ1SFoVO94kAv+mu7PXZ S6bNvTkgLKp5wPULryYCYq1ho5IOd83t+/6V85zKRc1fs3ULIGcC7mfhbGECDwH1ol6D MlEB1oiKryuuJKWwqhf9cS88NFRZbuRQFt7VY= 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; b=l4dsDXbQpLoJtFwCgLAnxRyC0g7OV/7VGvxybKuPKU7pQAu0UB8yDi+F5A+0ASyowP ofAoLR39UhDCBwgcpxlqDmaW9avusbOGuJ49aSDMMAZMwkqdgeKxCj+wfnJHWa9Ozgdd lcCcnAwhKdgahJo1YPp60vjCToTEM42FEEN2g= MIME-Version: 1.0 Received: by 10.224.104.93 with SMTP id n29mr1987181qao.193.1273442776234; Sun, 09 May 2010 15:06:16 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.229.220.66 with HTTP; Sun, 9 May 2010 15:06:16 -0700 (PDT) In-Reply-To: References: Date: Sun, 9 May 2010 15:06:16 -0700 X-Google-Sender-Auth: 4940e7b41469aa5b Message-ID: Subject: Re: Hadoop support for hbase From: Stack To: general@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Fri, May 7, 2010 at 10:34 AM, Dhruba Borthakur wrote: > 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 like this idea. It can be a little tough keeping up with latest state of the 0.20 "append" patch set. Having the set all applied in the one well-known place will make collaboration and discussion of the current state of 0.20 "append" the easier. Would hbase be the only party interested in such a branch? (Scribe?) St.Ack