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
Accumulo >> mail # user >> HBase rowkey design guidelines


Copy link to this message
-
Re: HBase rowkey design guidelines
Well, yes and no.

Smaller keys still mean less network traffic, potentially less IO, and
maybe faster operations if you're trying to do application logic. Using
data or default or just d probably doesn't matter in the long term
(although there are certainly cases where it might).
On Dec 3, 2013 11:57 PM, "David Medinets" <[EMAIL PROTECTED]> wrote:

> http://hbase.apache.org/book/rowkey.design.html - unless I am
> misunderstanding much of the advice given for HBase simply doesn't apply to
> Accumulo. For example "Try to keep the ColumnFamily names as small as
> possible, preferably one character (e.g. "d" for data/default)."
>
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