Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 5358 invoked from network); 9 Nov 2009 08:46:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Nov 2009 08:46:13 -0000 Received: (qmail 90658 invoked by uid 500); 9 Nov 2009 08:46:12 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 90578 invoked by uid 500); 9 Nov 2009 08:46:12 -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 90568 invoked by uid 99); 9 Nov 2009 08:46:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Nov 2009 08:46:12 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jwriteclub@gmail.com designates 209.85.223.179 as permitted sender) Received: from [209.85.223.179] (HELO mail-iw0-f179.google.com) (209.85.223.179) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Nov 2009 08:46:09 +0000 Received: by iwn9 with SMTP id 9so2501572iwn.30 for ; Mon, 09 Nov 2009 00:45:49 -0800 (PST) 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 :from:date:message-id:subject:to:content-type; bh=qgv7zzbE+wMU9LjbRp5MyLEdJRFwv7mdhhig8k+lb2k=; b=YhKZv9yfIEPORnT1RW5q/69AAIwBGb0r9ZBYiDATvKuxr+Zvj1uV21MNKOc6Frh50V ZquRaIJSe3o6PoihDwuDS9RvTL1M+L0UU65GCU8658AJtyutWM27KrTawp7zwNSE13iz 2b9U+s3c3nqJBAcVNUHKBn0i6RmaUgFWHlbZk= 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=m3rVfLmbcFxkNKVXZYCJlrd3EpqzZ9ZR+7DK4Tjdp/Np01/SaKRKLzmZZJa95jkczg O26X/hGgnV0oPySrmpNFfaHdvDlKaZM5+opH6MoCg312/M8oKPEV2kGpa/mqPiQDbo2h MloBtVQ9MxTroQ6NwUXY4J2BDUrzm6D/HRCwE= MIME-Version: 1.0 Received: by 10.231.21.157 with SMTP id j29mr3661774ibb.28.1257756349115; Mon, 09 Nov 2009 00:45:49 -0800 (PST) In-Reply-To: <214c385b0911081217g3834c13av52dccd79b4daf738@mail.gmail.com> References: <214c385b0911081108t68314495qd0892edcf158856f@mail.gmail.com> <81d01c0911081155h2a7b7b93sa888dc28ff0427ae@mail.gmail.com> <214c385b0911081217g3834c13av52dccd79b4daf738@mail.gmail.com> From: "Christopher O'Connell" Date: Mon, 9 Nov 2009 01:45:29 -0700 Message-ID: <81d01c0911090045p42e533eaq9d575f9e8203117f@mail.gmail.com> Subject: Re: Update API To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=00151774098c672e700477ec38ff --00151774098c672e700477ec38ff Content-Type: text/plain; charset=ISO-8859-1 Actually, I discovered that limit is only in trunk when testing externalJ. I ended up using a hacky hack to only read 500 lines at a time and then rewrite update seq to since+500. That way I can "chunk" it myself. ~ Christopher On Sun, Nov 8, 2009 at 1:17 PM, Matt Goodall wrote: > 2009/11/8 Christopher O'Connell : > > Just as a quick aside on the changes API, as a couple of people helped me > > figure out last night in the IRC channel, do be careful about grabbing > the > > canges API if its very large, as some JSON processing libraries take > obscene > > amounts of space to decode a JSON object that large. > > > > I don't think it's on the wiki, but limit=n works for _changes > > True for trunk but, sadly, not for the 0.10.x series. A workaround is > to use the continuous feed - each change arrives on its own line as a > JSON object so memory use can stay nice and low. > > I do wonder about the implementation of limit a little, the default > seems a little arbitrary ;-). > > Limit = list_to_integer(couch_httpd:qs_value(Req, "limit", > "1000000000000000")), > > Surely the limit should either default to infinite or something that > the client might sensibly handle, say 1000? > > Note: there's also a new descending=(true|false) _changes arg in trunk > too ... although I can't think of a usecase for it. > > - Matt > > > > > ~ Christopher > > > > On Sun, Nov 8, 2009 at 12:08 PM, Matt Goodall >wrote: > > > >> 2009/11/8 Andrew Melo : > >> > Oh, I'm sorry, I think I misspoke. I was looking for the API that will > >> > notify me when a new document is added to the database. > >> > >> I think this is what you're looking for: > >> > >> http://wiki.apache.org/couchdb/HTTP_database_API#Changes > >> > >> - Matt > >> > >> > > >> > thanks, > >> > Andrew > >> > > >> > On Sun, Nov 8, 2009 at 12:59 PM, Dave Ray wrote: > >> >> There's also a page on the Wiki here: > >> >> > >> >> > >> > http://wiki.apache.org/couchdb/How_to_intercept_document_updates_and_perform_additional_server-side_processing > >> >> > >> >> but I would trust the test suite more :) > >> >> > >> >> Dave > >> >> > >> >> On Sun, Nov 8, 2009 at 1:24 PM, Andrew Melo > >> wrote: > >> >>> On Sun, Nov 8, 2009 at 12:18 PM, Paul Davis < > >> paul.joseph.davis@gmail.com> wrote: > >> >>>> Andrew, > >> >>>> > >> >>>> Don't forget the Futon test suite. There's an update_documents.js > test > >> >>>> that is probably the most authoritative source of info on that. To > my > >> >>>> knowledge no one has started a wiki page. > >> >>>> > >> >>>> Paul > >> >>> > >> >>> Paul, > >> >>> > >> >>> Thanks for the pointer. I'll try and grok those files. > >> >>> > >> >>> Best regards, > >> >>> Andrew > >> >>> > >> >>> > >> >>>> > >> >>>> On Sun, Nov 8, 2009 at 12:57 PM, Andrew Melo < > andrew.melo@gmail.com> > >> wrote: > >> >>>>> Forgive me everyone, but my google-fu is having trouble finding > the > >> >>>>> documentation for the updates API for the newer version of Couch. > Can > >> >>>>> someone point me in the right direction? > >> >>>>> > >> >>>>> Thanks, > >> >>>>> Melo > >> >>>>> -- > >> >>>>> > >> >>>>> -- > >> >>>>> Andrew Melo > >> >>>>> Andrew.Melo@gmail.com > >> >>>>> > >> >>>> > >> >>> > >> >>> > >> >>> > >> >>> -- > >> >>> > >> >>> -- > >> >>> Andrew Melo > >> >>> Andrew.Melo@gmail.com > >> >>> > >> >> > >> > > >> > > >> > > >> > -- > >> > > >> > -- > >> > Andrew Melo > >> > Andrew.Melo@gmail.com > >> > > >> > > > --00151774098c672e700477ec38ff--