Hi, Sorry I dont have enough context here. The region name format is designed to be semi-backwards compatible, so you should be able to use 'true' for the new field and use the resulting string in searches in META even with old region names in META.
-ryan On Mon, Nov 15, 2010 at 5:03 PM, Ted Yu <[email protected]> wrote: > Ryan: > It originated from the following call against 0.20.6: > > HRegionInfo.createRegionName(tableName, null, ZEROES); > > On Mon, Nov 15, 2010 at 4:48 PM, Ryan Rawson <[email protected]> wrote: > >> Why are you calling this method? >> >> Despite it being 'public', users are not expected to talk to the >> filesystem directly. Your Warranty would be void if you did so :-) >> >> -ryan >> >> >> On Mon, Nov 15, 2010 at 4:44 PM, Ted Yu <[email protected]> wrote: >> > Can someone tell me when false should be specified for newFormat ? >> > >> > Thanks >> > >> > On Mon, Nov 15, 2010 at 2:15 PM, Stack <[email protected]> wrote: >> > >> >> I made an issue to cover J-D's suggestion, HBASE-3236, that lists what >> >> Ted is looking for. Its pegged against 0.90.1 but if a new RC, we can >> >> include it then. >> >> >> >> St.Ack >> >> >> >> >> >> >> >> On Mon, Nov 15, 2010 at 9:23 PM, Jean-Daniel Cryans < >> [email protected]> >> >> wrote: >> >> > I think it's worth going at greater lengths to document that kind of >> >> > "breakage", maybe a page in the book? Stuff like "What's new" and >> >> > "Incompatibilities" that we can easily link to. >> >> > >> >> > J-D >> >> > >> >> > On Mon, Nov 15, 2010 at 12:38 PM, Ryan Rawson <[email protected]> >> >> wrote: >> >> >> That is correct, those classes were deprecated in 0.20, and now gone >> in >> >> 0.90. >> >> >> >> >> >> Now you will want to use HTable and Result. >> >> >> >> >> >> Also Filter.getNextKeyHint() is an implementation detail, have a look >> >> >> at the other filters to get a sense of what it does. >> >> >> >> >> >> On Mon, Nov 15, 2010 at 12:33 PM, Ted Yu <[email protected]> >> wrote: >> >> >>> Just a few findings when I tried to compile our 0.20.6 based code >> with >> >> this >> >> >>> new release: >> >> >>> >> >> >>> HConstants is final class now instead of interface >> >> >>> RowFilterInterface is gone >> >> >>> org.apache.hadoop.hbase.io.Cell is gone >> >> >>> org.apache.hadoop.hbase.io.RowResult is gone >> >> >>> constructor >> >> >>> >> >> >> HColumnDescriptor(byte[],int,java.lang.String,boolean,boolean,int,boolean) >> >> >>> is gone >> >> >>> Put.setTimeStamp() is gone >> >> >>> org.apache.hadoop.hbase.filter.Filter has added >> >> >>> getNextKeyHint(org.apache.hadoop.hbase.KeyValue) >> >> >>> >> >> >>> If you know the alternative to some of the old classes, please >> share. >> >> >>> >> >> >>> On Mon, Nov 15, 2010 at 2:51 AM, Stack <[email protected]> wrote: >> >> >>> >> >> >>>> The first hbase 0.90.0 release candidate is available for download: >> >> >>>> >> >> >>>> http://people.apache.org/~stack/hbase-0.90.0-candidate-0/<http://people.apache.org/%7Estack/hbase-0.90.0-candidate-0/> >> <http://people.apache.org/%7Estack/hbase-0.90.0-candidate-0/> >> >> <http://people.apache.org/%7Estack/hbase-0.90.0-candidate-0/> >> >> >>>> >> >> >>>> HBase 0.90.0 is the major HBase release that follows 0.20.0 and the >> >> >>>> fruit of the 0.89.x development release series we've been running >> of >> >> >>>> late. >> >> >>>> >> >> >>>> More than 920 issues have been closed since 0.20.0. Release notes >> are >> >> >>>> available here: http://su.pr/8LbgvK. >> >> >>>> >> >> >>>> HBase 0.90.0 runs on Hadoop 0.20.x. It does not currently run on >> >> >>>> Hadoop 0.21.0. HBase will lose data unless it is running on an >> >> >>>> Hadoop HDFS 0.20.x that has a durable sync. Currently only the >> >> >>>> branch-0.20-append branch [1] has this attribute. No official >> releases >> >> >>>> have been made from this branch as yet so you will have to build >> your >> >> >>>> own Hadoop from the tip of this branch or install Cloudera's CDH3 >> [2] >> >> >>>> (Its currently in beta). CDH3b2 or CDHb3 have the 0.20-append >> patches >> >> >>>> needed to add a durable sync. See CHANGES.txt [3] in >> >> >>>> branch-0.20-append to see list of patches involved. >> >> >>>> >> >> >>>> There is no migration necessary. Your data written with HBase >> 0.20.x >> >> >>>> (or with HBase 0.89.x) is readable by HBase 0.90.0. A shutdown and >> >> >>>> restart after putting in place the new HBase should be all thats >> >> >>>> involved. That said, once done, there is no going back to 0.20.x >> once >> >> >>>> the transition has been made. HBase 0.90.0 and HBase 0.89.x write >> >> >>>> region names differently in the filesystem. Rolling restart from >> >> >>>> 0.20.x or 0.89.x to 0.90.0RC0 will not work. >> >> >>>> >> >> >>>> Should we release this candidate as hbase 0.90.0? Take it for a >> spin. >> >> >>>> Check out the doc. Vote +1/-1 by November 22nd. >> >> >>>> >> >> >>>> Yours, >> >> >>>> The HBasistas >> >> >>>> P.S. For why the version 0.90 and whats new in HBase 0.90, see >> slides >> >> >>>> 4-10 in this deck [4] >> >> >>>> >> >> >>>> 1. >> >> http://svn.apache.org/viewvc/hadoop/common/branches/branch-0.20-append >> >> >>>> 2. http://archive.cloudera.com/docs/ >> >> >>>> 3. >> >> >>>> >> >> >> http://svn.apache.org/viewvc/hadoop/common/branches/branch-0.20-append/CHANGES.txt >> >> >>>> 4. >> http://hbaseblog.com/2010/07/04/hug11-hbase-0-90-preview-wrap-up/ >> >> >>>> >> >> >>> >> >> >> >> >> > >> >> >> > >> >
