Hi Rams, IMHO, you need to go through http://hbase.apache.org/book.html and the book "HBase:The Definitive Guide" to get a deeper understanding of HBase. It will help you in designing your system.
There is no magical trick to design the most efficient/best RowKey without knowing the detailed requirements, constraints and carrying out couple of experiments. HTH, Anil On Tue, Nov 27, 2012 at 8:44 PM, Ramasubramanian < ramasubramanian.naraya...@gmail.com> wrote: > Hi, > > Thanks!! > > Can someone help in suggesting what is the best rowkey that we can use in > this scenario. > > Regards, > Rams > > On 27-Nov-2012, at 10:37 PM, Suraj Varma <svarma...@gmail.com> wrote: > > > Ian Varley's excellent HBaseCon presentation is another great resource. > > http://ianvarley.com/coding/HBaseSchema_HBaseCon2012.pdf > > > > On Mon, Nov 26, 2012 at 5:43 AM, Doug Meil > > <doug.m...@explorysmedical.com> wrote: > >> > >> Hi there, somebody already wisely mentioned the link to the # of CF's > >> entry, but here are a few other entries that can save you some heartburn > >> if you read them ahead of time. > >> > >> http://hbase.apache.org/book.html#datamodel > >> > >> http://hbase.apache.org/book.html#schema > >> > >> http://hbase.apache.org/book.html#architecture > >> > >> > >> > >> > >> > >> On 11/26/12 5:28 AM, "Mohammad Tariq" <donta...@gmail.com> wrote: > >> > >>> Hello sir, > >>> > >>> You might become a victim of RS hotspotting, since the cutomerIDs > will > >>> be sequential(I assume). To keep things simple Hbase puts all the rows > >>> with > >>> similar keys to the same RS. But, it becomes a bottleneck in the long > run > >>> as all the data keeps on going to the same region. > >>> > >>> HTH > >>> > >>> Regards, > >>> Mohammad Tariq > >>> > >>> > >>> > >>> On Mon, Nov 26, 2012 at 3:53 PM, Ramasubramanian Narayanan < > >>> ramasubramanian.naraya...@gmail.com> wrote: > >>> > >>>> Hi, > >>>> Thanks! Can we have the customer number as the RowKey for the customer > >>>> (client) master table? Please help in educating me on the advantage > and > >>>> disadvantage of having customer number as the Row key... > >>>> > >>>> Also SCD2 we may need to implement in that table.. will it work if I > >>>> have > >>>> like that? > >>>> > >>>> Or > >>>> > >>>> SCD2 is not needed instead we can achieve the same by increasing the > >>>> version number that it will hold? > >>>> > >>>> pls suggest... > >>>> > >>>> regards, > >>>> Rams > >>>> > >>>> On Mon, Nov 26, 2012 at 1:10 PM, Li, Min <m...@microstrategy.com> > wrote: > >>>> > >>>>> When 1 cf need to do split, other 599 cfs will split at the same > >>>> time. So > >>>>> many fragments will be produced when you use so many column families. > >>>>> Actually, many cfs can be merge to only one cf with specific tags in > >>>>> rowkey. For example, rowkey of customer address can be uid+'AD', and > >>>>> customer profile can be uid+'PR'. > >>>>> > >>>>> Min > >>>>> -----Original Message----- > >>>>> From: Ramasubramanian Narayanan [mailto: > >>>>> ramasubramanian.naraya...@gmail.com] > >>>>> Sent: Monday, November 26, 2012 3:05 PM > >>>>> To: user@hbase.apache.org > >>>>> Subject: Expert suggestion needed to create table in Hbase - Banking > >>>>> > >>>>> Hi, > >>>>> > >>>>> I have a requirement of physicalising the logical model... I have a > >>>>> client model which has 600+ entities... > >>>>> > >>>>> Need suggestion how to go about physicalising it... > >>>>> > >>>>> I have few other doubts : > >>>>> 1) Whether is it good to create a single table for all the 600+ > >>>> columns? > >>>>> 2) To have different column families for different groups or can it > >>>> be > >>>>> under a single column family? For example, customer address can we > >>>> have > >>>> as > >>>>> a different column family? > >>>>> > >>>>> Please help on this.. > >>>>> > >>>>> > >>>>> regards, > >>>>> Rams > >> > >> > -- Thanks & Regards, Anil Gupta
