Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 30 Aug 2012 04:42:09 +1100 (NCT)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <705142879.12745.1346262129441.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <459005337.12082.1308249168310.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (HBASE-3999) book.xml - Compression Upgrade
 Concerns
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Hofhansl resolved HBASE-3999.
----------------------------------

    Resolution: Fixed

We have section C.6 in the book now. I think we can close this.
(Unless you think this needs a more prominent mentioning)
                
> book.xml - Compression Upgrade Concerns 
> ----------------------------------------
>
>                 Key: HBASE-3999
>                 URL: https://issues.apache.org/jira/browse/HBASE-3999
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Doug Meil
>            Assignee: Jean-Daniel Cryans
>            Priority: Minor
>
> Spawned from comment on HBASE-3998
> (snip)
> Jean-Daniel Cryans added a comment - 16/Jun/11 18:00
> We should also add something about what happens when altering a family that was uncompressed to LZO or GZ, and vice versa. This just came up in the IRC channel: if I enable compression on a column family that was not previously compressed, what is needed to get the existing data in that column family compressed ?
> (snip)
> I'd suggest putting a new section under Appendix/Compression called something like "Upgrade Considerations" because this could either be compression algorithm upgrades (LZO->new version of LZO), or schema changes (as JD pointed out) where you are changing compression algorithms.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira