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 b.candler@pobox.com designates
 64.74.157.62 as permitted sender)
Resent-From: brian@uk.tiscali.com
Resent-Date: Thu, 30 Jul 2009 08:43:15 +0100
Resent-Message-ID: <20090730074315.GB9281@uk.tiscali.com>
Resent-To: user@couchdb.apache.org
Received-SPF: None identity=pra; client-ip=208.72.237.18;
 receiver=mk-inboundfilter-2-a-1.b2b.uk.tiscali.com;
 envelope-from="SRS0=3c/H=DX=gmail.com=jochenkempf@bounce2.pobox.com";
 x-sender="jochenkempf@gmail.com"; x-conformance=sidf_compatible
Received-SPF: Pass identity=mailfrom; client-ip=208.72.237.18;
 receiver=mk-inboundfilter-2-a-1.b2b.uk.tiscali.com;
 envelope-from="SRS0=3c/H=DX=gmail.com=jochenkempf@bounce2.pobox.com";
 x-sender="SRS0=3c/H=DX=gmail.com=jochenkempf@bounce2.pobox.com";
 x-conformance=sidf_compatible; x-record-type="v=spf1"
Received-SPF: Pass identity=helo; client-ip=208.72.237.18;
 receiver=mk-inboundfilter-2-a-1.b2b.uk.tiscali.com;
 envelope-from="SRS0=3c/H=DX=gmail.com=jochenkempf@bounce2.pobox.com";
 x-sender="postmaster@sepia.pobox.com"; x-conformance=sidf_compatible;
 x-record-type="v=spf1"
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
 :content-type;
 b=QCMQfXeFCsu0bD4tSwSu6cHjpxzcG/aYVOf1Dgp6I4rp6UZvhiAEgo6L+7ptCeHzH7
 zSlDpgtn8qawYBqSobi5oMxYU2uvmZT99+7Q4v3BE8hzAGX6RNM4YGy+bWwPwn/V6KZa
 cW9zJUvwl3LJ2T0Iz/szbaMLA+jUYmdE3yld4=
MIME-Version: 1.0
In-Reply-To: <20090729093554.GC10984@uk.tiscali.com>
References: <6d692b470907271733o3edca47aj4b4664fb0abeb559@mail.gmail.com>
 <20090729093554.GC10984@uk.tiscali.com>
From: Jochen Kempf <jochenkempf@gmail.com>
Date: Wed, 29 Jul 2009 23:48:59 -0400
Message-ID: <6d692b470907292048v11b96ea4hdac0d0e5afc525b6@mail.gmail.com>
Subject: Re: Problems with reduce in view appear when record size > 6
To: Brian Candler <B.Candler@pobox.com>
Content-Type: multipart/alternative; boundary=0016362835ea38c6b9046fe430e3
Resent-Date: Thu, 30 Jul 2009 08:43:15 +0100

--0016362835ea38c6b9046fe430e3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Brian,

guessing that you refer to this page incremental
map<http://damienkatz.net/2008/02/incremental_map_1.html>the
corresponding reduce function would be as follows, right (the final
reduce result is slightly changed, being a hash now)?
I am asking as I am still not absolutely firm with that topic...

map =>
"
  function(doc) {
  emit(doc["_id"], [doc["_id"], doc["_rev"], doc["var1"], doc["var2"],
doc["var3"], doc["var4"], doc["var5"]]);
  }
"

reduce =>
"
  function(key, values, combine) {
        var result = {ids:[], revs:[], variables:[]}
          if (combine) {
            for (i in values) {
              result.ids.push(values[i].ids);
              result.revs.push(values[i].revs);
              result.variables.push(values[i].variables);
            }
          } else {
            for (i in values) {
              result.ids.push(values[i][0]);
              result.revs.push(values[i][1]);
              result.variables.push([values[i][2], values[i][3],
values[i][4], values[i][5], values[i][6]]);
            }
          }
        return result;
      }
"


>
> Yes, one of ids, revs or variables is undefined :-)
>
> You can use 'log' to see what values are being passed into your reduce
> function.
>
> As a guess, I'd say that a re-reduce operation is taking place: 'combine'
> will be true, 'key' will be null, and 'values' will be the output of a
> previous reduce operation.
>
> That is: your reduce function must be written in such a way as to be able
> to
> process values generated by a previous reduce function, as well as values
> emitted by a document. The Wiki talks about this further.
>

--0016362835ea38c6b9046fe430e3--