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 >> should i use compression?


Copy link to this message
-
Re: should i use compression?
Prakash,

  Yes, I would recommend Snappy Compression.

On Wed, Apr 3, 2013 at 10:18 AM, Prakash Kadel <[EMAIL PROTECTED]> wrote:
> Thanks,
>     is there any specific compression that is recommended of the use case i have?
>    Since my values are all null will compression help?
>
>  I am thinking of using prefix data_block_encoding..
> Sincerely,
> Prakash Kadel
>
>
> On Apr 3, 2013, at 10:55 PM, Ted Yu wrote:
>
>> You should use data block encoding (in 0.94.x releases only). It is helpful
>> for reads.
>>
>> You can also enable compression.
>>
>> Cheers
>>
>>
>> On Wed, Apr 3, 2013 at 6:42 AM, Prakash Kadel <[EMAIL PROTECTED]>wrote:
>>
>>> Hello,
>>>    I have a question.
>>>    I have a table where i store data in the column qualifiers(the values
>>> itself are null).
>>>    I just have 1 column family.
>>>   The number of columns per row is variable (1~ few thousands)
>>>
>>> Currently i don't use compression or the data_block_encoding.
>>>
>>> Should i?
>>> I want to have faster reads.
>>>
>>> Please suggest.
>>>
>>>
>>> Sincerely,
>>> Prakash Kadel
>

--
Kevin O'Dell
Systems Engineer, Cloudera
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