Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 56F50D4D5 for ; Sat, 1 Dec 2012 20:21:23 +0000 (UTC) Received: (qmail 47829 invoked by uid 500); 1 Dec 2012 20:21:21 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 47784 invoked by uid 500); 1 Dec 2012 20:21:21 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 47773 invoked by uid 99); 1 Dec 2012 20:21:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2012 20:21:21 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.210.175] (HELO mail-ia0-f175.google.com) (209.85.210.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2012 20:21:14 +0000 Received: by mail-ia0-f175.google.com with SMTP id z3so1239025iad.34 for ; Sat, 01 Dec 2012 12:20:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=pRMlKgom7RUXCP2GK+LdIxk03sLm/z5JqVCe5E+xgH8=; b=Qef6DW61etwEqk1Ko2lb/lpnpFBD+xN6lKJsGhYoQzkXwNj5BBezYi80lxRIFTJKaO kO6lNkUMVNO9xddHMcUoPjCQcnz2zMFmcbqc7j3jryScQhycMHWWlA+WUhx2LDXnzV7N tTeja5zpSU9vqbulD/4DOLPaz5a58iBYEiDg7P35okJaFUU3hdNmxnyyczKrQ4kbu6ZV VVE9DA3VN1YKoeA/eotLqQi1r1jgOGZ4t2e/kcty4X82iGSJZny38FTqlpFg5aEps+wq y6AdfvjtdOCBB9kf3/DFqbp1ru1xhEt4AIr0MW0b7VF89PQkxlN0Hvw+mQFf7temJQ0j rqXA== MIME-Version: 1.0 Received: by 10.50.36.194 with SMTP id s2mr2072312igj.56.1354393253632; Sat, 01 Dec 2012 12:20:53 -0800 (PST) Received: by 10.64.97.36 with HTTP; Sat, 1 Dec 2012 12:20:53 -0800 (PST) Date: Sat, 1 Dec 2012 15:20:53 -0500 Message-ID: Subject: Change the compression algorythme From: Jean-Marc Spaggiari To: user Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQnrMwaA+D9nWeEmPxYnQv9Jm9KdQSALbFKeTcMyyKY8g4vpgEchjdBpNj6oNceFNQp9TNO6 X-Virus-Checked: Checked by ClamAV on apache.org 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