Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@minotaur.apache.org Received: (qmail 25749 invoked from network); 2 Apr 2009 19:34:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Apr 2009 19:34:26 -0000 Received: (qmail 65126 invoked by uid 500); 2 Apr 2009 19:34:26 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 65095 invoked by uid 500); 2 Apr 2009 19:34:26 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 65085 invoked by uid 99); 2 Apr 2009 19:34:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2009 19:34:26 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of nitayj@gmail.com designates 209.85.217.164 as permitted sender) Received: from [209.85.217.164] (HELO mail-gx0-f164.google.com) (209.85.217.164) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2009 19:34:19 +0000 Received: by gxk8 with SMTP id 8so1605530gxk.5 for ; Thu, 02 Apr 2009 12:33:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=ljwHQf1dakd3PA/gu0ItA5jHPV/m023fHg4ztwWiGik=; b=Dzq+Jg2+LSLZnGA+16ye9K+ykRuRKzUfvnBYhKHJkO1duP7OKljoEjm0s4eY9lXhx/ wl3ZWitARr7ORpShkmnCBbMUWr1tahFZC7HJ92DThgRXpkTDpqwhASUSgDHH+tb2gNG8 pmP9lLr9PCWCqGAfmEyjJI7cBIKeA6+ZiXSZA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ZsXs9gf+oasRRHwN2FjtEqqwMc3nsVRgDe0D8a54tWWX0ftcFgcVDHwMYdTfbl88R+ 4s40qC664bn+gwdSuNtw6fNZ8nhYmNFo5H+KZQHBpmFsz7CBp7PEs8DDSA29JgFue82J APBdR84CZTQ+4BAScVz7gS/qZa8lzt3n2W2LU= MIME-Version: 1.0 Received: by 10.150.156.20 with SMTP id d20mr680999ybe.102.1238700837901; Thu, 02 Apr 2009 12:33:57 -0700 (PDT) In-Reply-To: <054301c9b3d0$e43cd050$acb670f0$@com> References: <78568af10904012351m257dbee3i6e9674259f12688f@mail.gmail.com> <7c962aed0904020009r50b931c4pf9dc7e208e497d4b@mail.gmail.com> <78568af10904020013y7ca77716wdab49e3a1e7e314a@mail.gmail.com> <7c962aed0904020042n1d3b7b21mc2d105852607a55b@mail.gmail.com> <054301c9b3d0$e43cd050$acb670f0$@com> Date: Thu, 2 Apr 2009 12:33:57 -0700 Message-ID: <82b0992a0904021233nd33d0c4n90c8264465dd1de2@mail.gmail.com> Subject: Re: thinking about hbase 0.20 From: Nitay To: hbase-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary=000e0cd6a9526d1bb104669783e8 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd6a9526d1bb104669783e8 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I think it'd be good to have HBASE-1302 in for 0.20. On Thu, Apr 2, 2009 at 1:23 PM, Jonathan Gray wrote: > I personally feel very strongly about the need to finish all things > surrounding 1249. > > Erik and I have spent an enormous amount of time designing and > re-implementing the client, api, implementation of gets/puts/deletes, > etc... > > Without these things HBase will be improved but will still be doing all > sorts of silly things in implementation that cause problems with high > numbers of columns, poor performance on deletes, and basically never taking > advantage of "early-out" scenarios requiring entire scans in almost every > case today. > > The good news is that it's mostly done. We're waiting to get a solid 1234 > patch committed and tested before breaking it apart again. It's > significant > change but well thought out and mostly complete. Now is the time to make > these more radical changes, there's a full migration either way. > > JG > > > -----Original Message----- > > From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of > > stack > > Sent: Wednesday, April 01, 2009 11:42 PM > > To: hbase-dev@hadoop.apache.org > > Subject: Re: thinking about hbase 0.20 > > > > That'd be ideal. > > > > Regards what features should be in 0.20.0, we should start in weeding > > the > > list of 77 issues currently filed against 0.20.0 here: > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mo > > de=hide&sorter/order=DESC&sorter/field=priority&resolution=- > > 1&pid=12310753&fixfor=12313474 > > . > > > > St.Ack > > > > On Thu, Apr 2, 2009 at 9:13 AM, Ryan Rawson wrote: > > > > > Thinking about a migration, practically speaking this would be > > doable: > > > > > > - Flush and compact everything. Get rid of reference files from > > region > > > splits. > > > - Take each mapfile (ignore the index files), read the file in, write > > an > > > equivalent hfile out. > > > - Done! > > > > > > This can't be done while the cluster is online however. > > > > > > Any other suggestions? > > > > > > On Thu, Apr 2, 2009 at 12:09 AM, stack wrote: > > > > > > > I made HBASE-1215 as issue to cover migration from 0.19.x to > > 0.20.0. > > > > > > > > We have a migration 'system' already. You run ./bin/hbase migrate. > > Going > > > > from 0.19.0 to 0.20.0, we'll need to add a mapreduce job that > > rewrites > > > all > > > > hbase data to new format. It needs to be MR for those cases where > > data > > > is > > > > large. > > > > > > > > I thought at first that we could do lazy migration but after > > looking at > > > it, > > > > keeping up two key types in the one context looked too complex. > > > > > > > > St.Ack > > > > > > > > On Thu, Apr 2, 2009 at 8:51 AM, Ryan Rawson > > wrote: > > > > > > > > > hi all, > > > > > > > > > > it's been a long road, but it's time to start thinking about what > > will > > > > > conclusively be in 0.20. > > > > > > > > > > I'll let you fight that out a bit... personally I'd be happy with > > hfile > > > + > > > > > KeyValue. > > > > > > > > > > But, one last thing, what is our migration story going to be? > > > > > > > > > > -ryan > > > > > > > > > > > > > > --000e0cd6a9526d1bb104669783e8--