Return-Path: X-Original-To: apmail-gora-dev-archive@www.apache.org Delivered-To: apmail-gora-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6A07B1765C for ; Thu, 16 Oct 2014 18:55:35 +0000 (UTC) Received: (qmail 52441 invoked by uid 500); 16 Oct 2014 18:55:35 -0000 Delivered-To: apmail-gora-dev-archive@gora.apache.org Received: (qmail 52405 invoked by uid 500); 16 Oct 2014 18:55:35 -0000 Mailing-List: contact dev-help@gora.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@gora.apache.org Delivered-To: mailing list dev@gora.apache.org Received: (qmail 52382 invoked by uid 99); 16 Oct 2014 18:55:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Oct 2014 18:55:35 +0000 Date: Thu, 16 Oct 2014 18:55:35 +0000 (UTC) From: =?utf-8?Q?Kasper_S=C3=B8rensen_=28JIRA=29?= To: dev@gora.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (GORA-377) Implement gora-metamodel module MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/GORA-377?page=3Dcom.atlassian.j= ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D141740= 89#comment-14174089 ]=20 Kasper S=C3=B8rensen commented on GORA-377: -------------------------------------- Hi Lewis, * I'd be happy to help if I can with docs. Right now there are no gora.pro= perties or gora mappings available in the module. Actually this points to o= ne of my questions - how is this supposed to work... I imagine that the map= ping 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 tab= les towards the domain objects in Gora. * Regarding Map-Reduce ... Yes, currently MetaModel does not have any MR f= unctionality. It does have a way of splitting queries (QuerySplitter class)= so that they could transform into partitioned queries ... It does so by re= writing 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 m= ight not be optimal at all. In DataCleaner (an application that uses MetaMo= del quite heavily) this behaviour is sometimes applied, but only for partic= ular 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)