Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of zachary.zolton@gmail.com
 designates 74.125.46.30 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=sgfIsLICuPunhSASOot0ugmVrvlGhoF53Cxl2NYvkMAHOt29pOyOqxKE3reGXhy1tb
         GV0/c12hwFbPBDoRt3j5qAEmPDrCsPWsh8ne3IW5oDuBe/NN3jF6bjeAEzZC7w6aX+ou
         tWqIGVQhe+gfNbU7URis07DE3ViHUCofCorAg=
MIME-Version: 1.0
Date: Mon, 2 Mar 2009 12:32:30 -0600
Message-ID: <f728979f0903021032q367e5a48y242c95a54b203a6e@mail.gmail.com>
Subject: Pig, et al?
From: Zachary Zolton <zachary.zolton@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hey all,

Has anyone looked into how a high-level data-processing language could
integrate with CouchDB?

http://wiki.apache.org/pig/PigOverview
http://www.cs.cmu.edu/~olston/publications/sigmod08.pdf

I've been reading a bit about (fellow Apache project) Pig, which
implements features analogous to CouchDB views and combinative
operations over views. I'm guessing it's not a perfect fit =97otherwise
I wager I'd have heard some mention of it on this mailing list.

Lack of mention aside, the author seems to indicate that their
language/toolkit isn't a good fit for scenarios such as "real-time
data serving requirements", which I took to mean most web apps.

This leaves me with these questions:

  Can we do anything higher-level than one-off scripting of JavaScript view=
s?

  Would higher-level operations be better implemented as a client library D=
SL?

Sorry for rambling here, but I'd just like to spark some interest =97and
volunteer to do some research, given some direction from the Couch Dev
community...


Cheers,

Zach