Hi there,
I'd recommend reading the Schema Design chapter in the RefGuide because
there are some good tips and hard-learned lessons.
http://hbase.apache.org/book.html#schema
Also, all your examples use composite row keys (not a surprise, a very
common pattern) and one thing I would like to
What are your data access patterns?
Best Regards,
Sonal
Real Time Analytics for BigData https://github.com/sonalgoyal/crux
Nube Technologies http://www.nubetech.co
http://in.linkedin.com/in/sonalgoyal
On Fri, Jan 18, 2013 at 9:04 AM, Ramasubramanian Narayanan
Hi Sonal,
1. will fetch all demographic details of customer based on client ID
2. Fetch the particular type of address along with other demographic for a
client.. for example, HOME Physical address or HOME Telephone address or
office Email address etc.,
regards,
Rams
On Fri, Jan 18, 2013 at
How about client id as the rowkey, with column families as physical
address, email address, telephone address? within each cf, you could have
various qualifiers. For eg in physical address, you could have home Street,
office street etc.
Best Regards,
Sonal
Real Time Analytics for BigData
Hi Sonal,
In that case, the problem is how to store multiple physical address sets in
the same column family.. what rowkey to be used for this scenario..
A Physical address will contain the following fields (need to store
multiple physical address like this):
Physical address type :
A rowkey is associated with the complete row. So you could have client id
as the rowkey. Hbase allows different qualifiers within a column family, so
you could potentially do the following:
1. You could have qualifiers like home address street 1, home address
street 2, home address city, office
Hi,
Is there any other way instead of using HOME/Work/etc? we expect some 10
such types may come in future.. hence asking
regards,
Rams
On Fri, Jan 18, 2013 at 10:24 AM, Sonal Goyal sonalgoy...@gmail.com wrote:
A rowkey is associated with the complete row. So you could have client id
as the
