That’s funny; we just got out of a meeting discussing this. Yes, we can move the columns into the row key making a really tall table. I hope this will perform better than large # of columns. We will have to find a good delimiter which will work generically across the data set.
Ryan Rawson wrote: > > Also remember you might be able to convert to a tall table. Row keys can > be > compound and you can do partial left matches on them. Eg: > > Userid:timestamp:eventid > > now you have a tall table. Do prefix matches on the userid you want and > you > get results in chronological order. > > You can build equivalent indexes in hbase as in sql. You may find a design > like this alieviates the need for extremely wide rows. > > Good luck! > > On Jun 11, 2009 11:44 AM, "Billy Pearson" <[email protected]> > wrote: > > That might be a good idea but you might be able to redesign you layout of > the table > using a different key then the current one worth barnstorming. > > Billy > > > > "llpind" <[email protected]> wrote in message > news:[email protected]... > > Sorry I forgot to mention the overflow then overflows into new row keys > per > 10,000 column entries ... > > -- View this message in context: http://www.nabble.com/Help-with-Map-Reduce-program-tp23952252p23989319.html Sent from the HBase User mailing list archive at Nabble.com.
