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 >> KeyValue size in bytes compared to store files size


Copy link to this message
-
Re: KeyValue size in bytes compared to store files size
On Thu, Jan 16, 2014 at 1:00 AM, Amit Sela <[EMAIL PROTECTED]> wrote:

> ...
>
> Could such a compression ratio make sense in case of many qualifiers per
> row in a table (avg is 16 but in practice there are some rows with much
> more and even a small number of rows with hundreds of thousands...) ? If
> each KeyValue contains the rowkey, and the rowkeys contain more bytes than
> the qualifiers / values, than the rows repeat themselves in the HFile and
> actually make most of the HFile, right ?
>

If lots of repetition, yes.  You could test by counting uncompressed and
compressed tables.  You get same answer?
Yours,
St.Ack
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