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

Nick Dimiduk commented on HBASE-10756:
--------------------------------------

[~manukranthk] in mind of using complex types in rowkeys and qualifiers, have a 
look at the [Struct 
type|http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/types/Struct.html]
 and its helpers. They're designed to be used in combination with the 
OrderedBytes encoders for exactly this use case. See the 
[Ordered*|http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/types/package-frame.html]
 types in the same package, these are DataType API implementations backed the 
ordered encoders.

> Adding Data Types and Structured Row Keys in 0.89-fb HBase
> ----------------------------------------------------------
>
>                 Key: HBASE-10756
>                 URL: https://issues.apache.org/jira/browse/HBASE-10756
>             Project: HBase
>          Issue Type: New Feature
>          Components: Usability
>    Affects Versions: 0.89-fb
>            Reporter: Manukranth Kolloju
>            Assignee: Manukranth Kolloju
>             Fix For: 0.89-fb
>
>
> As an extension to some of the work done on Presto + HBase side, and also 
> inspired by some of the work done on open source and Pheonix, introducing 
> data types and structured row keys will enable the data base(hbase) to 
> de-couple database level optimizations from the application level schema. The 
> attempt is to provide a table definition & specification to define the row 
> key structure which can be composed as a composite struct composed of 
> primitive data types.
> The data base can make intelligent decisions of how to interpret the data. 
> For instance, having an understanding of the the structure of row key will 
> hint the database about the parts of the data that are valuable and can use 
> that information to construct indexes/bloom filters based on these parts of 
> the row key.
> This can be extended to the column qualifiers and Nested Types as well.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to