Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAGngS9fjk8R-p=-jap=Y9W5v6tH6vkRiBm0_02qbtNwZpC42QQ@mail.gmail.com>
References: 
 <CAPQV63Uja8z7r4Sfm=875_P88M0xAabs--suvom6Zpzdy_GgnA@mail.gmail.com>
	<CAGngS9fjk8R-p=-jap=Y9W5v6tH6vkRiBm0_02qbtNwZpC42QQ@mail.gmail.com>
Date: Sat, 1 Dec 2012 15:32:56 -0500
Message-ID: 
 <CAPQV63VPhX6Tzq1F6cGA+kk8kbAevU-jtN6RgN0uGpyRyy0N9g@mail.gmail.com>
Subject: Re: Change the compression algorythme
From: Jean-Marc Spaggiari <jean-marc@spaggiari.org>
To: user@hbase.apache.org
Content-Type: text/plain; charset=UTF-8

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 <kevin.odell@cloudera.com>:
> 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" <jean-marc@spaggiari.org>
> 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
>>
>