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: local policy)
Date: Tue, 6 Nov 2012 16:17:58 +0200
From: svilen <az@svilendobrev.com>
To: user@couchdb.apache.org
Subject: Re: Any sort order guarantee for key (value) argument of CouchDB
 reduce function?
Message-ID: <20121106161758.5e88a41d@eee-az>
In-Reply-To: 
 <CAGqoiQtRRFiDbTWAQEO122cpUpNUN0tb6o9rhGGw+UjU3PjuXQ@mail.gmail.com>
References: 
 <CAGqoiQuEYzRwUevgrZO=727VoYp6wwb0kuwXv78d1dpfPbhtwA@mail.gmail.com>
	<CAGqoiQtRRFiDbTWAQEO122cpUpNUN0tb6o9rhGGw+UjU3PjuXQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

no, see reponses to my thread "what's the order of docs/keys going into
reduce func?" from 22.09.

for small sets, it's reversed but that seems just a local consequence of
some algo.

ciao
svilen

On Tue, 6 Nov 2012 16:55:57 +0400
Vladislav Ponomarev <ponomarevvlad@gmail.com> wrote:

> Hello,
> 
> Per CouchDB guide, the reduce function signature looks like this:
> 
> function (key, values, rereduce) {
>     return ...; // some calculations happen here
> }
> 
> where the definition of first arguments is as follows:
> 
> >
> > when rereduce is false, then:
> >
> >    - key will be an array whose elements are arrays of the form
> > [key,id], where key is a key emitted by the map function and id is
> > that of the document from which the key was generated.
> >    - values will be an array of the values emitted for the
> > respective elements in keys.
> >
> >
> My question is: when rereduce is false, are there any guarantees
> regarding the order of key (or values) array elements? My gut feel
> (based on Reduce vs Rereduce chapter) is that keys, and respectively
> values, should be ordered, but I do not see any direct confirmation.
> 
> >
> Any ideas? Thank you!