[
https://issues.apache.org/jira/browse/HBASE-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nichole Treadway updated HBASE-3691:
------------------------------------
Attachment: hbase-snappy-3691-trunk-003.patch
Thanks for the patch...I made a few additional changes in HColumnDescriptor,
and I updated the test files to include snappy.
I noticed there are places in the hbase.avro classes where snappy support would
need to be added in. Is it ok to add these changes in the patch, or do the avro
classes need to be auto-generated somehow?
> Add compressor support for 'snappy', google's compressor
> --------------------------------------------------------
>
> Key: HBASE-3691
> URL: https://issues.apache.org/jira/browse/HBASE-3691
> Project: HBase
> Issue Type: Task
> Reporter: stack
> Priority: Critical
> Fix For: 0.92.0
>
> Attachments: hbase-snappy-3691-trunk-002.patch,
> hbase-snappy-3691-trunk.patch
>
>
> http://code.google.com/p/snappy/ is apache licensed.
> bq. Snappy is a compression/decompression library. It does not aim for
> maximum compression, or compatibility with any other compression library;
> instead, it aims for very high speeds and reasonable compression. For
> instance, compared to the fastest mode of zlib, Snappy is an order of
> magnitude faster for most inputs, but the resulting compressed files are
> anywhere from 20% to 100% bigger. On a single core of a Core i7 processor in
> 64-bit mode, Snappy compresses at about 250 MB/sec or more and decompresses
> at about 500 MB/sec or more.
> bq. Snappy is widely used inside Google, in everything from BigTable and
> MapReduce to our internal RPC systems. (Snappy has previously been referred
> to as "Zippy" in some presentations and the likes.)
> Lets get it in.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
