Inline below. On Tue, Aug 10, 2010 at 10:55 PM, Yu Bady <[email protected]> wrote: > Hi, > > > We are going to use HBase to store our large volume of pretty structured > data. > > Every day, we will have about 24 new roles added to one table. After three > months, there will be about 4,000,000,000 new rows in the table. >
Sounds fine. > By the way, in the table, each row will have about 8 column families and > each column family will have 2-3 columns. But each cell just contains 20 > bytes data. > Why 8 column families? You'll be doing accesses against individual column families? If you could do with yes, that'd be better but 8 should be fine. > > So I have following questions: > > 1. How many rows can HBase supports in one table? > I don't know. I know of tables of 30B small rows. > 2. After one year, there will be about 16,000,000,000 rows in the table. If > the row numbers are too large, is it helpful to solve the problem by > splitting the original table into several tables? How to split one table > into several tables? > How big are your cells? As far as hbase is concerned, there is no real difference hosting many vs one table. > 3. Any other suggestions? > Tell us more about how you intend to access the table -- the kinda of queries -- otherwise, sounds fine. Can you try things out in the small first to learn edgecases yourself first? St.Ack
