[jira] [Commented] (HBASE-3691) Add compressor support for 'snappy', google's compressor

2012-04-30 Thread Chris Waterson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13265059#comment-13265059
 ] 

Chris Waterson commented on HBASE-3691:
---

What is the likelihood that this could be back-ported to the 0.90.x branch?

> 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-003.patch, hbase-snappy-3691-trunk-004.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.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (HBASE-3691) Add compressor support for 'snappy', google's compressor

2012-05-01 Thread Chris Waterson (JIRA)

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

Chris Waterson updated HBASE-3691:
--

Attachment: hbase-snappy-0.90.6.patch

Yes, I have.  I've applied hbase-snappy-0.90.5.patch and it seems to be working 
on a small (but heavily loaded) HBase 0.90.6 cluster.

> 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-0.90.6.patch, 
> hbase-snappy-3691-trunk-002.patch, hbase-snappy-3691-trunk-003.patch, 
> hbase-snappy-3691-trunk-004.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.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (HBASE-3691) Add compressor support for 'snappy', google's compressor

2012-05-01 Thread Chris Waterson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13265877#comment-13265877
 ] 

Chris Waterson commented on HBASE-3691:
---

Urg, "I've applied hbase-snappy-0.90.6.patch..."

> 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-0.90.6.patch, 
> hbase-snappy-3691-trunk-002.patch, hbase-snappy-3691-trunk-003.patch, 
> hbase-snappy-3691-trunk-004.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.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira