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

Andrew Purtell commented on HBASE-7716:
---------------------------------------

If you are thinking of adding optional metadata to KVs, consider HBASE-7448.

What is the interplay with split policies? Split policy would be extended with 
the group group concept? How would a split policy know the starting and ending 
boundary of a row group?

Reminds me of "major key paths" in the Oracle NOSQL DB: 
http://www.oracle.com/technetwork/products/nosqldb/overview/key-value-497224.html
 . 
                
> Row Groups / Row Family / Entity Groups in HBase
> ------------------------------------------------
>
>                 Key: HBASE-7716
>                 URL: https://issues.apache.org/jira/browse/HBASE-7716
>             Project: HBase
>          Issue Type: New Feature
>          Components: Client, regionserver
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 0.98.0
>
>         Attachments: Entity Groups in HBase.txt
>
>
> This issue is to discuss the possible addition to the HBase data model for 
> "Row Groups".
> As we are nearing 1.0, discussing this for 0.98 seems the right time, 
> especially given that we have custom region split policies, local 
> transactions, and API overhaul around data types -> bytes. 
> Row Groups are semantic groupings of rows in the Hbase data model. All rows 
> within a given row group share the same row group key. 
> Row groups are similar to column families in HBase or locality groups in 
> BigTable, but transposed to rows instead of columns. All the rows within a 
> row group physically belong together, and served by a single region. This 
> means that region boundaries cannot split the row group. 
> Row groups are not predefined, and are dynamic. There can be one row group 
> per row. 
> Row keys are fully optional, and backwards compatible. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to