[HBASE-3732] New configuration option for client-side compression

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Assignee: Unassigned
• Reporter: Jean-Daniel Cryans
• Created: 04/Apr/11 22:45
• Updated: 12/Jun/22 17:29
• Resolved: 09/Apr/13 16:52

Description

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.

Issue Links

• is related to: HBASE-2182 rpc/ipc refactor; x-version compatibility, nio, async, enveloping, sane timeouts, etc.