can, may be build a secondary table in background with
> phonetic keys as row keys.
> http://en.wikipedia.org/wiki/Soundex
>
>
> hth,
> Abhishek
>
>
> -Original Message-
> From: Jason Huang [mailto:jason.hu...@icare.com]
> Sent: Tuesday, October 02, 2012 2:38
-Original Message-
From: Jason Huang [mailto:jason.hu...@icare.com]
Sent: Tuesday, October 02, 2012 2:38 PM
To: user@hbase.apache.org
Subject: Re: HBase table row key design question.
Thanks Mohammad.
The issue about phone number is that it tends to change over time and we think
name a
Thanks Mohammad.
The issue about phone number is that it tends to change over time and
we think name and DOB are more reliable. SSN is more unique but the
issue is that we can't force the user to provide it. Basically we have
limited information that can be used.
thanks,
Jason
On Tue, Oct 2, 20
Hi there, while this isn't an answer to some of the specific design
questions, this chapter in the RefGuide can be helpful for general design..
http://hbase.apache.org/book.html#schema
On 10/2/12 10:28 AM, "Jason Huang" wrote:
>Hello,
>
>I am designing a HBase table for users and hope to g
Hello Sir,
Although we should always try to keep the rowkey length as less as
possible, but still a short key that doesn't help much in faster data
access is also of no use. So, it totally depends on that particular use
case. However, in your case, how about using "phone number" as the rowkey
Hello,
I am designing a HBase table for users and hope to get some
suggestions for my row key design. Thanks...
This user table will have columns which include user information such
as names, birthday, gender, address, phone number, etc... The first
time user comes to us we will ask all these inf
