Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jchris@gmail.com designates
 209.85.198.241 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=gtseiTMbnY56qU6Prop5D2S3iFAh3QyUr0X5sb4YftRpFlNpUOGIDS0mS8+C4UuGmA
         mszAT6sI0Qe3o5NPrUbaGoXiiYO/zZoWXKspekuz8FnTdID/4M/4NOR/MAiD0gJovJbe
         +zTVvnvcjHi+5fTdKHYQ/woK/pERLH2ii/V+Q=
Message-ID: <e282921e0806130216w3d20dfdfh244ea5b491e12ee5@mail.gmail.com>
Date: Fri, 13 Jun 2008 02:16:29 -0700
From: "Chris Anderson" <jchris@grabb.it>
Sender: jchris@gmail.com
To: couchdb-user@incubator.apache.org
Subject: Re: Modifying fields
In-Reply-To: <7770A5DA-9B70-4C37-9075-1D3EB1E33FDF@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <48516A9B.5060401@gmail.com> <48519E04.8040304@gmail.com>
	 <567B2EFA-3E14-4A4B-9C0A-F27225B8715C@apache.org>
	 <4851B3D9.1040403@gmail.com>
	 <7770A5DA-9B70-4C37-9075-1D3EB1E33FDF@apache.org>

On Fri, Jun 13, 2008 at 1:53 AM, Jan Lehnardt <jan@apache.org> wrote:
>
> On Jun 13, 2008, at 01:40, Brad Schick wrote:
>
>> It would be interesting to know the load on the DB of doing something
>> like that inside the server versus sending and receiving all million
>> documents to the client.
>
> You'd save all HTTP handling. So things would be faster. We are at a
> point with CouchDB where we are working on getting it right and not
> getting it fast or adding features for all edge cases. I'm not saying that
> CouchDB will never get a feature that helps you, but it is not yet a
> priority.
>

That might be something doable via the view server / search query /
line-based json API. A job runner that you can submit jobs to wouldn't
be a bad way to obviate http connection issues. Send the job to the
data, they say. And then you could write job functions in any language
you want.

Building it as a plugin would solve the immediate issue, and allow
CouchDB's core to concentrate on getting it right. Plus job runners
just sound useful anyway, especially for things like functions that
clone a group-reduce result to a new database for further manipulation
and querying.

-- 
Chris Anderson
http://jchris.mfdz.com