[
https://issues.apache.org/jira/browse/METAMODEL-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738354#comment-13738354
]
Ian Varley commented on METAMODEL-13:
-------------------------------------
The basic way they do it is by overlaying a RDBMS schema / type system over top
of HBase. The schemas are created with CREATE TABLE commands, and stored in a
table inside HBase. They also deal with common byte encodings (e.g. binary
comparable INTs), though they plan to start using the richer datatype support
that's coming soon in HBase (see this article for more on that:
http://hortonworks.com/blog/data-types-schema/). I'd recommend diving into the
Phoenix code, it's quite robust and using it directly inside the Metamodel
module (rather than rewriting it) would probably give a big leg up to the HBase
adapter in Metamodel, including immediate support for mutations, server-side
aggregation, secondary indexes, etc.
There are, of course, a few cases where the underlying model of HBase doesn't
exactly match the relational model (e.g. the fact that rows can have any set of
columns, not predefined at runtime). Phoenix has some open issues to map these
more hbase-specific concepts into matching SQL abstractions (e.g.
https://github.com/forcedotcom/phoenix/issues/19 and
https://github.com/forcedotcom/phoenix/issues/5).
> HBase support for MetaModel
> ---------------------------
>
> Key: METAMODEL-13
> URL: https://issues.apache.org/jira/browse/METAMODEL-13
> Project: Metamodel
> Issue Type: New Feature
> Reporter: Kasper Sørensen
> Assignee: Sameer Arora
>
> We have a separate remote Git branch for this ticket: 'hbase-module'.
> Refer also to the original eobjects.org ticket:
> http://eobjects.org/trac/ticket/1120
--
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
