metamodel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ian Varley (JIRA)" <>
Subject [jira] [Commented] (METAMODEL-13) HBase support for MetaModel
Date Wed, 14 Aug 2013 17:09:48 GMT


Ian Varley commented on METAMODEL-13:

Valid points, especially in terms of not wanting the HBase metamodel adaptor to *require*
everything that comes with Phoenix (system table, coprocessor installation, specific byte
encodings, etc). Metamodel needs to work with raw HBase in the simplest way possible.

That said, for other standard SQL databases (like MySQL, Oracle, etc.), Metamodel does take
advantage of the query parser, query model, system tables, built in aggregations, etc., right?
The existence of Phoenix puts HBase in a class where it could be treated more like these than
like a raw row store. It can still conform to the universal set of functionality, but in a
way that's more like MySQL than it is like raw HBase.

So perhaps a better approach is to think of adding an *additional* module - there's the HBase
module that goes against raw HBase (what you've already built), and then in the future maybe
there's also an "HBase/Phoenix" module that goes against HBase with Phoenix in between. The
latter doesn't preclude the former. (My guess is that the benefits of using the Phoenix version--secondary
indexes, parallelization, mutability, schema management, high-performance aggregation--would
eventually be compelling enough to make it a common choice). If you agree, I'll file a JIRA
for that. :)
> HBase support for MetaModel
> ---------------------------
>                 Key: METAMODEL-13
>                 URL:
>             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 ticket:

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:

View raw message