[
https://issues.apache.org/jira/browse/HBASE-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935980#comment-13935980
]
stack commented on HBASE-10756:
-------------------------------
You've seen this work in trunk [~manukranthk]:
http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/types/package-frame.html
and the description of how it serializes here:
http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/util/OrderedBytes.html
A few of us have been chatting offline about possibility of all serializing
types the same way: e.g. Phoenix using the above types. If you fellas are
interested, we'd love to have you as part of the club.
Where would I read about how presto does serializations? Or is it currently in
the works?
> 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)
