[
https://issues.apache.org/jira/browse/GORA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174089#comment-14174089
]
Kasper Sørensen commented on GORA-377:
--------------------------------------
Hi Lewis,
* I'd be happy to help if I can with docs. Right now there are no
gora.properties or gora mappings available in the module. Actually this points
to one of my questions - how is this supposed to work... I imagine that the
mapping would be 99% inferred since MetaModel already does a lot of detection
of metadata. But of course I guess there will be mapping from metamodel tables
towards the domain objects in Gora.
* Regarding Map-Reduce ... Yes, currently MetaModel does not have any MR
functionality. It does have a way of splitting queries (QuerySplitter class) so
that they could transform into partitioned queries ... It does so by rewriting
the queries and introduce WHERE clauses and so on... I am not 100% sure that
will work (well) in all cases though, since those WHERE clauses might not be
optimal at all. In DataCleaner (an application that uses MetaModel quite
heavily) this behaviour is sometimes applied, but only for particular cases
where we know it works well.
> 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
>
> Attachments: GORA-377_patch1.diff
>
>
> 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)
