[
https://issues.apache.org/jira/browse/GORA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148366#comment-14148366
]
Renato Javier Marroquín Mogrovejo commented on GORA-377:
--------------------------------------------------------
IMHO Metamodel should provide access to the stores it already does. Gora should
keep on providing its query interface because in a way Gora abstracts other
stores data models, but we should add the ability to perform more complex
queries to whatever each data store we support.
The way I see it Gora has a different use case than Metamodel. Gora tries to
offer a simple <key, value> interface not caring what is behind. This, of
course, is good for some cases and not enough for others. Metamodel aims to
provide SQL-like API for querying datastores which would be similar to Apache
Phoenix, HiveQL, CQL, or others. I think we should add the capability to use
such access methods for people to retrieve data from underlying data stores but
keeping our data model abstraction i.e. a simple key, value api.
> Implement gora-metamodel module
> -------------------------------
>
> Key: GORA-377
> URL: https://issues.apache.org/jira/browse/GORA-377
> Project: Apache Gora
> Issue Type: New Feature
> Components: gora-metamodel
> Reporter: Lewis John McGibbney
> Fix For: 0.6
>
>
> There have been recent discussions [0] around implementing MetaModel [1] in a
> drive to improving the Gora Query model and functionality.
> This issue is merely a placeholder for implementing exctly that.
> [0] http://www.mail-archive.com/dev%40gora.apache.org/msg05149.html
> [1] http://metamodel.incubator.apache.org/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
