Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 5 Apr 2011 04:42:06 +0000 (UTC)
From: "Benoit Sigoure (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1829622591.34211.1301978526051.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <396032074.33696.1301957225724.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-3732) New configuration option for
 client-side compression
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Benoit Sigoure commented on HBASE-3732:
---------------------------------------

If you want {{Put}}/{{Result}} to do the conversion for you, that means the client needs to be aware of the schema of the table before it can start using it, right?  Because right now HBase clients don't know the schema, so it's something extra that they'd need to lookup separately, unless we add new fields in the {{.META.}} table that go along with each and every region.

> 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
>
>
> 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