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

Matt Corgan commented on HBASE-5313:
------------------------------------

Just noticed this jira.  I've been working on 
https://issues.apache.org/jira/browse/HBASE-4676.  In this trie format all the 
values are concatenated at the end of the block.  I haven't done anything with 
compressing them because they are generally small in my use cases, but seems 
like it would eventually be a good option.  I would think that the compression 
savings would be similar to the on-disk compression savings, but the benefit is 
that you have access to scan the keys while the data part of the block is still 
compressed.
                
> Restructure hfiles layout for better compression
> ------------------------------------------------
>
>                 Key: HBASE-5313
>                 URL: https://issues.apache.org/jira/browse/HBASE-5313
>             Project: HBase
>          Issue Type: Improvement
>          Components: io
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>
> A HFile block contain a stream of key-values. Can we can organize these kvs 
> on the disk in a better way so that we get much greater compression ratios?
> One option (thanks Prakash) is to store all the keys in the beginning of the 
> block (let's call this the key-section) and then store all their 
> corresponding values towards the end of the block. This will allow us to 
> not-even decompress the values when we are scanning and skipping over rows in 
> the block.
> Any other ideas? 

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

        

Reply via email to