[
https://issues.apache.org/jira/browse/METAMODEL-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739335#comment-13739335
]
Kasper Sørensen commented on METAMODEL-13:
------------------------------------------
Direct use of phoenix does have both pros and cons I think. Obviously it can
get us a long way fast, but the problem is IMO that phoenix does "too much" of
the same things as MetaModel's query engine does. We don't want to adapt too
many query models to one another, since mapping always is a big source of
issues. Another pitfall is that while phoenix might support a lot of cool
features, we only need to support those that are universal for all MetaModel
adaptors - anything else is "waste" in the sense that it isn't exposed in our
interface. For example, MetaModel has a predefined set of available aggregation
functions and all other functions besides those are not usable for us.
What I do like from phoenix, and want to reuse in some way (by dependency, by
inspiration or by replicating the code):
* Metadata discovery (not sure I understand what you mean by binary compatible
INTs, but also I am not a HBase expert).
* Server side aggregation (nice to have).
But I don't see us needing/wanting:
* The query parser and query model (seems like a huge chunk of phoenix)
* The system table that is created in HBase to describe columns etc. - this is
IMO very intrusive for a framework like MM.
* The JDBC API (although a generic MetaModel-JDBC API could be considered, but
not a one-off for this module only).
This might be a bit dissapointing if you're looking at MetaModel coming only
from a HBase perspective. But really the purpose of MetaModel isn't to be the
best driver for a single particular database, but to be the unification and
abstraction above them all, making it possible to write reusable code that
would fit any of the modules we have.
> 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
