[
https://issues.apache.org/jira/browse/HBASE-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-2404:
----------------------------------
Description:
We often recommend enabling LZO on tables, most users see big wins. LZO is
roughly comparable to BigTable LZW, and we get something like prefix
compression on keys. However, LZO is GPL licensed, so a series of install steps
are required: http://wiki.apache.org/hadoop/UsingLzoCompression . It's easy to
miss a step or get it wrong. If so, all writes on a table (re)configured to use
LZO will fail.
Hadoop, well, Java, has native support for gzip compression but it is too slow
generally; is a good option however for archival tables.
This issue is about considering bundling or creating a comparable alternate to
LZO which is ASF 2.0 license compatible.
was:
We often recommend enabling LZO on tables, most users see big wins. LZO is
roughly comparable to BigTable LZW, also the way HFile uses LZO has functional
equivalence to prefix compression on keys. However, LZO is GPL licensed, so a
series of install steps are required:
http://wiki.apache.org/hadoop/UsingLzoCompression . It's easy to miss a step or
get it wrong. If so, all writes on a table (re)configured to use LZO will fail.
Hadoop, well, Java, has native support for gzip compression but it is too slow
generally; is a good option however for archival tables.
This issue is about considering bundling or creating a comparable alternate to
LZO which is ASF 2.0 license compatible.
Updated confusing language.
> native fast compression codec
> -----------------------------
>
> Key: HBASE-2404
> URL: https://issues.apache.org/jira/browse/HBASE-2404
> Project: Hadoop HBase
> Issue Type: New Feature
> Reporter: Andrew Purtell
>
> We often recommend enabling LZO on tables, most users see big wins. LZO is
> roughly comparable to BigTable LZW, and we get something like prefix
> compression on keys. However, LZO is GPL licensed, so a series of install
> steps are required: http://wiki.apache.org/hadoop/UsingLzoCompression . It's
> easy to miss a step or get it wrong. If so, all writes on a table
> (re)configured to use LZO will fail.
> Hadoop, well, Java, has native support for gzip compression but it is too
> slow generally; is a good option however for archival tables.
> This issue is about considering bundling or creating a comparable alternate
> to LZO which is ASF 2.0 license compatible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
