hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3732) New configuration option for client-side compression
Date Thu, 02 Jun 2011 01:04:47 GMT

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

Jean-Daniel Cryans commented on HBASE-3732:
-------------------------------------------

I wouldn't call it a vote, since there's no voting process in Apache for requesting features.
Contributors submit patches whether the rest of the community likes it or not, then it's up
to the committers to get them into SVN if they want it or not.

My opinion is that this is something HBase should be doing by default, there are too many
advantages. I agree with Stack that it is easy to do at the application level, but then if
everyone starts doing then it really begs the question as to why isn't HBase doing it in the
first place.

> 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
>             Fix For: 0.92.0
>
>         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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message