Return-Path: 
 <user-return-9075-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org>
Delivered-To: apmail-couchdb-user-archive@www.apache.org
Received: (qmail 3314 invoked from network); 2 Mar 2010 17:46:20 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 2 Mar 2010 17:46:20 -0000
Received: (qmail 17537 invoked by uid 500); 2 Mar 2010 17:46:14 -0000
Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org
Received: (qmail 17505 invoked by uid 500); 2 Mar 2010 17:46:14 -0000
Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@couchdb.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@couchdb.apache.org>
List-Post: <mailto:user@couchdb.apache.org>
List-Id: <user.couchdb.apache.org>
Reply-To: user@couchdb.apache.org
Delivered-To: mailing list user@couchdb.apache.org
Received: (qmail 17490 invoked by uid 99); 2 Mar 2010 17:46:14 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Mar 2010 17:46:14 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of truemped@googlemail.com
 designates 209.85.219.211 as permitted sender)
Received: from [209.85.219.211] (HELO mail-ew0-f211.google.com)
 (209.85.219.211)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Mar 2010 17:46:05 +0000
Received: by ewy3 with SMTP id 3so360904ewy.35
        for <multiple recipients>; Tue, 02 Mar 2010 09:45:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=gamma;
        h=domainkey-signature:received:received:subject:mime-version
         :content-type:from:in-reply-to:date:cc:content-transfer-encoding
         :message-id:references:to:x-mailer;
        bh=16O0kZKjFpyXBdS930n2VFsra3pM0Ii9jFxIC29Qk7w=;
        b=LzZqJn51VJyoH+RuVNuvu3vmaSfWTkwqdW6hSa4ckcuF0BSrXTrnEgSMpmKfrqiT62
         PD3L6n8uHlyJJFwTOVfhubxP0Y1tMKgWVb6j+8TFOVJvL0g8tFuXgiExTg5Ip80yaafU
         Qna295R9M28ESXsIAPWx/48nuoZikN47xfM3k=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=subject:mime-version:content-type:from:in-reply-to:date:cc
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=tvssYIZhkoOn9R091ZLjWSlmWFijBOhIOK+Wq8tK8tsY2G9DUmNNAIF9YAQS1sEnVl
         QkbevQ9m9QUvre12nIPHAZ2b6vh7i0PL9VlOujuM9QCERQ+S1lj712A7PYtnwnZA94j2
         DkU+DN9KgC0FFnxIe5rpxadERAxzymO5itVao=
Received: by 10.213.97.88 with SMTP id k24mr4925868ebn.86.1267551943569;
        Tue, 02 Mar 2010 09:45:43 -0800 (PST)
Received: from vandusen.neofonie.priv (crt-01-tr.neofonie.de [91.213.91.28])
        by mx.google.com with ESMTPS id 13sm3203446ewy.13.2010.03.02.09.45.41
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Tue, 02 Mar 2010 09:45:41 -0800 (PST)
Subject: Re: Hitting the reduce overflow boundary
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Daniel Truemper <truemped@googlemail.com>
In-Reply-To: <ea2499da1003020830g672d7e6dg6e913b83a22ab36d@mail.gmail.com>
Date: Tue, 2 Mar 2010 18:45:40 +0100
Cc: dev@couchdb.apache.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <71DE26DB-136C-43CD-B6C3-F51B00FC6C8F@googlemail.com>
References: <ea2499da1003020830g672d7e6dg6e913b83a22ab36d@mail.gmail.com>
To: user@couchdb.apache.org
X-Mailer: Apple Mail (2.1077)

Moving this to user@c.a.o?!

> I'm using this view at work:
> http://friendpaste.com/3CtGyg5IczkxNV3rWRdalB
>=20
> Unfortunately, after adding a new document today, it stopped working
> due to the reduce overflow error checking. In this case, I think the
> document I added had 20 currencies to be inserted into the interest
> value, whereas the former largest doc had only 9.
>=20
> For now, I've just disabled the reduce_limit, but it would be nice if
> the heuristic could be tuned (as the comment in default.ini says). If
> there's some better way of writing my view, that would be fine as
> well, of course.
I think you view could need some improvement but it is kind of hard to =
guess what you are trying to do. Maybe you could provide a little more =
details about it!?

Best
Daniel=