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 3F4A29580 for ; Tue, 6 Mar 2012 15:56:18 +0000 (UTC) Received: (qmail 39541 invoked by uid 500); 6 Mar 2012 15:56:18 -0000 Delivered-To: apmail-gora-dev-archive@gora.apache.org Received: (qmail 39511 invoked by uid 500); 6 Mar 2012 15:56:18 -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 39501 invoked by uid 99); 6 Mar 2012 15:56:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Mar 2012 15:56:18 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [128.149.139.106] (HELO mail.jpl.nasa.gov) (128.149.139.106) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Mar 2012 15:56:12 +0000 Received: from mail.jpl.nasa.gov (altvirehtstap01.jpl.nasa.gov [128.149.137.72]) by smtp.jpl.nasa.gov (Switch-3.4.3/Switch-3.4.3) with ESMTP id q26FtoP5030891 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO) for ; Tue, 6 Mar 2012 07:55:50 -0800 Received: from ALTPHYEMBEVSP20.RES.AD.JPL ([128.149.137.83]) by ALTVIREHTSTAP01.RES.AD.JPL ([128.149.137.72]) with mapi; Tue, 6 Mar 2012 07:55:49 -0800 From: "Mattmann, Chris A (388J)" To: "dev@gora.apache.org" Date: Tue, 6 Mar 2012 07:55:48 -0800 Subject: Re: Apache Gora March board report (draft) Thread-Topic: Apache Gora March board report (draft) Thread-Index: Acz7sZlp4A43TW25TxGR2bFDLqdQ/w== Message-ID: References: <0274B8AA-1589-4DED-8472-DE6E267690E5@jpl.nasa.gov> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Source-IP: altvirehtstap01.jpl.nasa.gov [128.149.137.72] X-Source-Sender: chris.a.mattmann@jpl.nasa.gov X-AUTH: Authorized X-Virus-Checked: Checked by ClamAV on apache.org Hey Lewis, Gotcha, no problem. One option is simply to remove the sqlbuilder library and to replace SqlStore with stubbed out methods that throw Exceptions and that simply don't work. Then we ship Gora 0.2, with a note saying don't use SqlStore. Then if folks complain and want to use it, we ask that they help to write the method implementations using an ALv2 compatible library. Would Derby be useful here, or Hypersonic SQL? Both of those are ALv2 compatible I think. Cheers, Chris On Mar 6, 2012, at 7:40 AM, Lewis John Mcgibbney wrote: > Hi Chris, >=20 > We'll in all honesty, I think it's best for me to provide a brief summar= y. >=20 > We need to remove our dependency upon and use of the healthmarketscience > sqlbuilder libary. Used very little in SqlStore class [0]. The problem I > ran into when looking into this was that unfortunately JOOQ doesn't suppo= rt > data definition language constructs which is exactly what we require. > Although this is in the pipeline (for JOOQ), I have a feeling that it may > be some way off. I did however run into a couple of examples of > implementing similar functionality to what we require, unfortunately I go= t > distracted and haven't had time to go back to it. I have included all of = my > resources on the offending issue on our Jira so anyone trying to pick it = up > would really be starting off from where I got to. This is the blocking > issue here and unfortunately it doesn't look like something legal guys ca= n > help out with, it simply a case of understanding exactly what functionali= ty > we require then finding a replacement and someone that can code it in usi= ng > a more suitably licensed library. >=20 > If it is for the sake of pushing out with a Gora 0.2 release as per your > requirement's E.g. archive gora-sql then I would probably back this for t= he > time being... I am not using the gora-sql module, and in all honesty I > don't think that many others are hence the level of interest to get this > module up to scratch! >=20 > I began a thread a week or so ago, and to be honest the gora-sql issue wa= s > the only blocked in my opinion. >=20 > Thanks for chiming in on this one. >=20 > Lewis >=20 >=20 > [0] > http://svn.apache.org/viewvc/gora/trunk/gora-sql/src/main/java/org/apache= /gora/sql/store/SqlStore.java?view=3Dmarkup >=20 > On Tue, Mar 6, 2012 at 3:29 PM, Mattmann, Chris A (388J) < > chris.a.mattmann@jpl.nasa.gov> wrote: >=20 >> +1 from me, Lewis, Looks awesome. RE: gora-sql: what are the next steps >> there? >> Is it something the legal committee can help out with? At worst, I'd >> imagine, we >> could move gora-sql to a non-released area of SVN and then push forward >> with >> an 0.2 that doesn't include it? >>=20 >> Cheers, >> Chris >>=20 >> On Mar 6, 2012, at 7:26 AM, Lewis John Mcgibbney wrote: >>=20 >>> Hi All, >>>=20 >>> Time of month again, we have monthly reporting for the first three mont= hs >>> after graduation so please review and comment accordingly. >>> I'll get it committed as of >>>=20 >>> Apache Gora >>>=20 >>> The Apache Gora open source framework provides an in-memory data model >> and >>> persistence for big data. Gora supports persisting to column stores, ke= y >>> value stores, document stores and RDBMSs, and analyzing the data with >>> extensive Apache Hadoop MapReduce support. >>>=20 >>> Project Releases >>>=20 >>> The last official project release was made on 24/09/2011 which was the >>> 0.1.1-incubating release (2nd whilst in the Incubator). >>> Although there have been some commits to three Gora modules, some >> remaining >>> issues still need to be addressed before we are ready to roll out a 0.2 >>> release. >>> This is rather frustrating, as the main issue which blocks a 0.2 releas= e >> is >>> a licensing issue on the gora-sql store. It is widely acknowledged that >>> although >>> gora-sql is the least used module, it is the one which requires attenti= on >>> to rectify this >>> licensing issue. >>>=20 >>> Overall Project Activity since last report >>>=20 >>> Since graduation all documentation, and infrastructure has been >> successfully >>> migrated over to TLP status. We've witnessed development and committs t= o >>> three >>> datastores and a number of issues addressed as a result. It is safe to >> say >>> that the gora-hbase >>> store seems to be attracting the most development, however there are al= so >>> a number of issues which have recently been opened for the gora-cassand= ra >>> module. >>> In the last report we stated that there were two new modules in the >> process >>> of being >>> integrated into the project (namely gora-accumulo and gora-solr), howev= er >>> due to blocking issues >>> with releases for Solr and Accumulo, we are not able to release the gor= a >>> modules. >>>=20 >>> How has the community developed since the last report? >>>=20 >>> The Gora mailing lists have seen some activity with regards to >>> gora-accumulo, >>> however generally speaking traffic was quite low for the month until th= is >>> report. >>> We do however have some excellent news that we are submitting an >>> application >>> to Google Summer of Code. The project comprises a gora-dynamodb (Amazon >>> Dynamo >>> DB) module again making best efforts to open up Gora to a wider audienc= e. >>>=20 >>> Changes to PMC & Committers >>>=20 >>> Since VOTE'ing Keither Turner on to the team no new members have been >>> accepted >>> into the Gora development team. Additionally, no new VOTE'ing has taken >>> place. >>>=20 >>> PMC and Committer diversity >>>=20 >>> We currently have committers from a wide variety of projects including, >>> Nutch, Tika, OODT, Camel, Solr, Accumulo & Hadoop (this is not an >>> exhaustive list). There is work to be >>> done with the Avro implementations, so once we are 100% ready to work o= n >>> these issues, >>> we will be looking to interest members of the Avro community in Gora. >>>=20 >>> Project Branding or Naming issues >>>=20 >>> We recently sorted out all branding and trademark issues through >> trademarks@ >>> . >>> As this has been addressed there is no more to add at this stage. >>>=20 >>> Legal issues >>>=20 >>> We currently have an issue with one particular library being used withi= n >> the >>> gora-sql store. It is the communities intention to remove this LGPL >>> licensed library >>> from the codebase replacing it with implementations from JOOQ an ASL 2.= 0 >>> licensed library. >>> The re-write of the gora-sql module building from the JOOQ library has >> been >>> delayed >>> until after our 0.2 release. >>>=20 >>> -- >>> *Lewis* >>=20 >>=20 >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Chris Mattmann, Ph.D. >> Senior Computer Scientist >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> Office: 171-266B, Mailstop: 171-246 >> Email: chris.a.mattmann@nasa.gov >> WWW: http://sunset.usc.edu/~mattmann/ >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Adjunct Assistant Professor, Computer Science Department >> University of Southern California, Los Angeles, CA 90089 USA >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>=20 >>=20 >=20 >=20 > --=20 > *Lewis* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattmann@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++