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 Plain View
HBase >> mail # user >> Change the compression algorythme


+
Jean-Marc Spaggiari 2012-12-01, 20:20
+
Kevin Odell 2012-12-01, 20:27
Copy link to this message
-
Re: Change the compression algorythme
Perfect, thanks.

I will use the hbase.regionserver.codecs option to make sure the new
algorithm is working fine.

JM

2012/12/1, Kevin O'dell <[EMAIL PROTECTED]>:
> JM,
>
> You are correct. Just disable the table, alter the compression, and then
> major and minor compactions will run their course.
>
> Please remember to run the compression test first to make sure there is
> nothing wrong with the new algorithm.
> On Dec 1, 2012 3:21 PM, "Jean-Marc Spaggiari" <[EMAIL PROTECTED]>
> wrote:
>
>> Hi,
>>
>> What's the right way to change the compression algorythme for a cf?
>>
>> Can I simply disable the table, alter the table with the new
>> compression alg info, and enable it back? As a result, I will still
>> have a table compressed with the previous algorythme, but at some
>> point in the future, it will slowly move to the new one when
>> compactions are occuring?
>>
>> That mean that one table can have more than one compression alg used
>> at a time, right?
>>
>> Or this is not possible and I need to make sure it's fully
>> un-compressed before I enable another compression algorythme?
>>
>> Thanks,
>>
>> JM
>>
>
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