Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 18098 invoked from network); 28 Aug 2009 19:02:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Aug 2009 19:02:19 -0000 Received: (qmail 94915 invoked by uid 500); 28 Aug 2009 19:02:18 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 94819 invoked by uid 500); 28 Aug 2009 19:02:18 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 94802 invoked by uid 99); 28 Aug 2009 19:02:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Aug 2009 19:02:17 +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 fabio.forno@gmail.com designates 209.85.217.221 as permitted sender) Received: from [209.85.217.221] (HELO mail-gx0-f221.google.com) (209.85.217.221) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Aug 2009 19:02:08 +0000 Received: by gxk21 with SMTP id 21so2901657gxk.3 for ; Fri, 28 Aug 2009 12:01:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=XjMQ1OnnbevmODgZ+2bn8haSp4srCA/mPNTDl2hJYbc=; b=R+0zxn7bh0z/DpbSYcXPkOjkaYSHQIZiY6jYTDTayUf5MxH01JiH5aPMhJ7yKxxXFj y4Zi3faUdmaALeQfJbgJt/jD79uBiiOpHDpT6t1gs3L+6PRB6/haAMn7J2ik5O09iSbD odblgMJNhUwxTc+qgkUO/j/jhyz4tvjPqm/YY= 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; b=q3CTN/1WNfwlHNzzVMwB2w9ASo0G0sB+R63zCmp7PLdyCL20Ovz4LEK5fHhKa/s+bx YQzB+FwM5KCWNd+8OLfPSRRKsZdD8otYHrMFvYUj2wt63EbBGOt324o/um6RsR613ppx hUzsaUHoLftO9WchWXZEnNHh9n8PVh2i32uos= MIME-Version: 1.0 Received: by 10.90.225.5 with SMTP id x5mr1172313agg.87.1251486107731; Fri, 28 Aug 2009 12:01:47 -0700 (PDT) In-Reply-To: References: <2fd53c3a0908280841v25f03385i39812fd3ef34f6de@mail.gmail.com> Date: Fri, 28 Aug 2009 21:01:47 +0200 Message-ID: <2fd53c3a0908281201la5d22f6u8e46ae0056e79435@mail.gmail.com> Subject: Re: 0.9 to 0.10 breaking changes From: Fabio Forno To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Fri, Aug 28, 2009 at 5:47 PM, Paul Davis wrote: >> >> Why less then half? Suppose I must merge two docs A,B where I'm >> counting the occurrences of a set of items ans size(A) >> size(B), >> size(out) would be less than size(input), but more than half of it >> > > I don't follow. Can you paste some pseudo code? > Perhaps I'm thinking of a case where reduce is not supposed to work in that way. I've a map producing these intermediate documents key -> set of features then the reduce takes the set of features and does the merge. So let's have after the map: k1 -> {F1, F2, F3, F4, F5} k1 -> {F1, F3} the reduce is called with [{F1, F2}, {F1, F2, F3, F4, F5}], for which I return {F1', F2, F3', F4, F5} (the features are not simple keys, but are complex objects which are transformed during reduce) in this case I'm reducing the result, but the output is greater the half the size of the input. For what I've understood this would fail, wouldn't it? -- Fabio Forno, Ph.D. Bluendo srl http://www.bluendo.com jabber id: ff@jabber.bluendo.com