On Wed, Jan 20, 2010 at 1:43 AM, Gaurav Vashishth <[email protected]>wrote:
> > In order to store the high volume live data, I was thinking of designing > the > table structure and two options came into my mind > Because the incoming stream rate is so high, you want it spread across all servers? > > 1. Can we forcefully set the range in which region server will operate? > Like, If row with this partuclar ID come than this most goes to x region > server. If that is possible, then possibly I can have only one table in > cluster and can have dedicated region servers for them. > > Why do you want to do the above? What happens if the server dies? > 2. Another approach is to have multiple tables, I will manage this at my > code level and will insert the records in appropriate tables. > > Table will have only one column family with less than 20 qualifiers. > You could do this. Or have one table and design the key so the incoming stream of writes are spread across the cluster; e.g. hash key values? How are you going to access the data? Thats also an important input designing keys. St.Ack > > Plase help where Im missing or I'm totally way off? > > Thanks, > > Gaurav > -- > View this message in context: > http://old.nabble.com/HBase%3A-Designing-Table-structure-tp27239038p27239038.html > Sent from the HBase User mailing list archive at Nabble.com. > >
