Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> Use of MD5 as row keys - is this safe?


Copy link to this message
-
Re: Use of MD5 as row keys - is this safe?
On Mon, Jul 23, 2012 at 9:58 AM, Jonathan Bishop <[EMAIL PROTECTED]>wrote:

> Hi,
> Thanks everyone for the informative discussion on this topic.
>
> I think that for project I am involved in I must remove the risk, however
> small, of a row key collision, and append the original id (in my case a
> long) to the hash, whatever hash I use. I don't want to be in the situation
> where occasionally something goes wrong and needing to eliminate the
> possibility of a collision.
>
> I was confused by a discussion in a book I was reading on HBase, "HBase in
> Action", which used MD5 directly as the row key, leaving the impression
> that this was a completely reliable way of creating unique row keys from
> strings.
>

The book talks about hashing as well as salting. I'll add notes to it about
possible collisions while using hashing. Thanks for pointing this out.
>
> Jon
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB