[
https://issues.apache.org/jira/browse/METAMODEL-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13737848#comment-13737848
]
Ian Varley commented on METAMODEL-13:
-------------------------------------
I see there's already some work done here, which is cool. An HBase module would
be nifty.
In addition, have you looked into Phoenix
(https://github.com/forcedotcom/Phoenix)? It's a JDBC "skin" on HBase which
supports highly optimized read / write interactions with HBase through a JDBC /
SQL interface. It's not fully functional (for example, it can't perform JOINs),
nor is it fully standard (for example, it uses "UPSERT" rather than "INSERT"
and "UPDATE"), so to work seamlessly in Metamodel I think it would still have
to be a separate provider (i.e. it wouldn't just fall under the standard JDBC
bucket). But even so, using it internally within the module might be a faster,
simpler route for integrating HBase into metamodel rather than going directly
against the HBase client API. Additionally, it provides a lot of capabilities
that would be difficult to replicate against the API directly, like aggregation
functions, secondary indexes, etc. Something to consider.
> 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
