Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of bchesneau@gmail.com designates
 209.85.220.211 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=kMzozEomYKs57pQVmAI0ERiwJYb1PrBc+0S89m6kOo3YiKL0OUvFXiTlBbXN1Vzz06
         fEyCkImHu3a+g9H0ZdY/yed9fDOw8VKGjGQFjZ4NNluN/7vU6Eijg7GZ+hVtWzSp09Tg
         jDRr8Oz/8IosdbpNzIF32hJRNc6fu1lFyrf8E=
MIME-Version: 1.0
In-Reply-To: <e282921e0906141104g10ab9613mb71771a22b5c37e7@mail.gmail.com>
References: <b7cd8ed10906100325m2aba0b9cuf9efba013b02af1a@mail.gmail.com>
	 <b7cd8ed10906100606v7d283f68o45dc757c5489f944@mail.gmail.com>
	 <e282921e0906100855t371bb7caufc9eab81eb475302@mail.gmail.com>
	 <b7cd8ed10906100924p391ba9a0we4ed75e15b611fb2@mail.gmail.com>
	 <f728979f0906101425y58b840a3lc588a63115991267@mail.gmail.com>
	 <20090611195504.GB20617@translab.its.uci.edu>
	 <59801549-09E3-4903-BA9A-0D0C35AC65BB@apache.org>
	 <e282921e0906141104g10ab9613mb71771a22b5c37e7@mail.gmail.com>
Date: Mon, 15 Jun 2009 08:30:58 +0200
Message-ID: <b7cd8ed10906142330p2ecc4191k4f714f42a3dc6282@mail.gmail.com>
Subject: Re: calulate doc popularity with couchdb map/reduce
From: Benoit Chesneau <bchesneau@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2009/6/14 Chris Anderson <jchris@apache.org>:
> On Sun, Jun 14, 2009 at 3:07 AM, Jan Lehnardt<jan@apache.org> wrote:
>>
>> On 11 Jun 2009, at 21:55, James Marca wrote:
>>
>>> On Wed, Jun 10, 2009 at 04:25:13PM -0500, Zachary Zolton wrote:
>>>>
>>>> So, another +1 for chainable map-reduce...? (-_^)
>>>
>>> And +1 from me too.
>>>
>>> I am completely ignorant of Erlang and the CouchDB internals, but why
>>> is map/reduce output (all the view docs I see in the directory as
>>> .whatever files) any different than regular CouchDB databases? =A0It
>>> seems logical that the same tools that apply to a CouchDB database
>>> should apply to view files as well, so one can map/reduce against view
>>> without having to manually convert it back from view results into
>>> another CouchDB database.
>>
>> The fundamental problem is that a reduced result can no longer keep
>> track of which docs took part in creating this value. For incremental
>> updates (knowing what to recompute when only a single doc changed)
>> needs this.
>>
>
> I wrote some Erlang code to copy a reduce query to another database
> for further sorting / viewing. I then realized it was not usable in a
> multi-node cluster so I abandoned the idea of putting it in CouchDB.
> Instead I plan to rewrite it in Ruby. It would seriously be about 6
> lines of code so I'll see what I can do.
>
>
Maybe this isn't the right method to do it but how Hadoop do ? Think
it's possible to chain map/reduce in it, isn't it ? In a real
map/reduce model you should be able to chain them. And I think it's
possible for grouped reduce since you send k/v .

Obviously making 4 HTTP calls to do display only one list of data
depending on the same key is too much. It's perfectly manageable in a
classic application but not for couchapps via ajax. Too much calls to
do it. obviously it can be done by an external or an internal handler,
but so why not having a way i couchdb to do it ?

- beno=EEt