hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Day" <allen...@gmail.com>
Subject Re: How to enforce the uniqueness of the row keys
Date Fri, 19 Sep 2008 22:44:06 GMT
I'm curious about this too.  What is best practice to use to generate
row keys?  Do we have an equivalent of a sequence / auto_increment in
hbase?

-Allen

On Fri, Sep 19, 2008 at 2:31 PM, Ding, Hui <hui.ding@sap.com> wrote:
> But these creates another single point of failure, which is another
> potential bottleneck, right?
>
> -----Original Message-----
> From: Jim Kellerman [mailto:Jim.Kellerman@microsoft.com]
> Sent: Friday, September 19, 2008 1:28 PM
> To: hbase-user@hadoop.apache.org
> Subject: RE: How to enforce the uniqueness of the row keys
>
> A GUID, MD5 hash, SHA-1 or Jenkins Hash (in
> org.apache.hadoop.hbase.util.JenkinsHash) are all mechanisms for
> generating unique row keys.
>
> ---
> Jim Kellerman, Powerset (Live Search, Microsoft Corporation)
>
>
>> -----Original Message-----
>> From: Ding, Hui [mailto:hui.ding@sap.com]
>> Sent: Friday, September 19, 2008 11:17 AM
>> To: hbase-user@hadoop.apache.org
>> Subject: How to enforce the uniqueness of the row keys
>>
>> Seems hbase does not care about that, but for certain applications we
>> need to make sure a key is unique (hopefully without a query into the
>> hbase to see if the key has already been used?)
>> Do you tend to use some GUID outside hbase? What is the preferred
>> approach?
>>
>> Thanks!
>
>

Mime
View raw message