hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-3999) book.xml - Compression Upgrade Concerns
Date Wed, 29 Aug 2012 17:42:09 GMT

     [ 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

View raw message