You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Pradeep Gollakota (JIRA)" <ji...@apache.org> on 2013/07/17 04:18:49 UTC
[jira] [Commented] (HBASE-3732) New configuration option for
client-side compression
[ https://issues.apache.org/jira/browse/HBASE-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710623#comment-13710623 ]
Pradeep Gollakota commented on HBASE-3732:
------------------------------------------
I'd like to reopen discussion on this ticket. I have a slightly different use case that I'm considering for client side compression (sorry if this isn't the right forum for this question).
I have a scenario where clients are in a different network topology than the hbase cluster. The bandwidth between the clients and the cluster is limited. Since the client buffers writes, is there any mechanism in place for compressing the over the wire transfers?
> New configuration option for client-side compression
> ----------------------------------------------------
>
> Key: HBASE-3732
> URL: https://issues.apache.org/jira/browse/HBASE-3732
> Project: HBase
> Issue Type: New Feature
> Reporter: Jean-Daniel Cryans
> Attachments: compressed_streams.jar
>
>
> We have a case here where we have to store very fat cells (arrays of integers) which can amount into the hundreds of KBs that we need to read often, concurrently, and possibly keep in cache. Compressing the values on the client using java.util.zip's Deflater before sending them to HBase proved to be in our case almost an order of magnitude faster.
> There reasons are evident: less data sent to hbase, memstore contains compressed data, block cache contains compressed data too, etc.
> I was thinking that it might be something useful to add to a family schema, so that Put/Result do the conversion for you. The actual compression algo should also be configurable.
--
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