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 paul.joseph.davis@gmail.com
 designates 209.85.146.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=UXHEltSt+j+ZEl6oaMoAmqyxo6Kqm6v0kw1U+Az1AxzMXhuVzRxDHjosaHKnDL7+rM
         abrluu8NLVti8PxeywOi1wgI/kawUAbkd0Ns7og3IoMKdSnSyPnWcdkjJ9igg0cyh0by
         2YYUYmmmA40Q9M8oeyYs04yJsC6m9m3ZHBL4E=
Message-ID: <49F8AA60.7020207@gmail.com>
Date: Wed, 29 Apr 2009 12:28:32 -0700
From: Paul Davis <paul.joseph.davis@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Re: Array being chunked in reduce
References: <26650b020904291210q28d6a62bkf4a2692d101c4798@mail.gmail.com>
In-Reply-To: <26650b020904291210q28d6a62bkf4a2692d101c4798@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Ross Bates wrote:
> Hi All  - I have about 600 of documents with 3 attributes:
>
> parent, child, level
>
> When I run the following map/reduce everything looks correct at first in
> that I get an array back where the key is the level and the value is a
> collection of arrays that have share the same level value. So if there were
> 5 unique levels there would be 5 rows
>
> function(doc) {
>     emit( parseInt(doc.level), [doc.child,doc.parent]);
> };
>
>
> function(a,b){
> return b;
> }
>
>
> The problem is that when I run this on a larger data set the value array
> starts getting chunked into arbitrary sizes (50, 83, etc....) When I say
> chunked, the row has a bunch of additional nested arrays to store the
> key/value.
>
> Is there some sort of max array size imposed by couch db?
>
> Many Thanks,
> Ross
>
>   
Ross,

Firstly, the chunked bits you're seeing is couchdb running rereduce on 
your reduce output. The full signature of a reduce function is:

    function(keys, values, rereduce)

Where rereduce is a boolean that flags if the function is being called 
on its own output.

Also, the function as you have it would eventually tip over as its 
returning too much data. For your particular use case I would suggest 
omitting the reduce function entirely and then doing a selection on the 
map and any post-processing client side.

HTH,
Paul Davis