You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2017/04/05 18:33:41 UTC

[jira] [Commented] (HBASE-16594) ROW_INDEX_V2 DBE

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

Sean Busbey commented on HBASE-16594:
-------------------------------------

did this get fixed as a part of the parent jira?

> ROW_INDEX_V2 DBE
> ----------------
>
>                 Key: HBASE-16594
>                 URL: https://issues.apache.org/jira/browse/HBASE-16594
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Performance
>            Reporter: binlijin
>            Assignee: binlijin
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-16594-master_v1.patch, HBASE-16594-master_v2.patch
>
>
> See HBASE-16213, ROW_INDEX_V1 DataBlockEncoding.
> ROW_INDEX_V1 is the first version which have no storage optimization, 
> ROW_INDEX_V2 do storage optimization: store every row only once, store column family only once in a HFileBlock.
> ROW_INDEX_V1 is : 
> /** 
>  * Store cells following every row's start offset, so we can binary search to a row's cells. 
>  * 
>  * Format: 
>  * flat cells 
>  * integer: number of rows 
>  * integer: row0's offset 
>  * integer: row1's offset 
>  * .... 
>  * integer: dataSize 
>  * 
> */
> ROW_INDEX_V2 is :
>  * row1 qualifier timestamp type value tag
>  *          qualifier timestamp type value tag
>  *          qualifier timestamp type value tag
>  * row2 qualifier timestamp type value tag
>  * row3 qualifier timestamp type value tag
>  *          qualifier timestamp type value tag
>  * .... 
>  * integer: number of rows 
>  * integer: row0's offset 
>  * integer: row1's offset 
>  * .... 
>  * column family
>  * integer: dataSize 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)