Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CC4D3351F for ; Sat, 30 Apr 2011 16:46:26 +0000 (UTC) Received: (qmail 14266 invoked by uid 500); 30 Apr 2011 16:46:25 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 14238 invoked by uid 500); 30 Apr 2011 16:46:25 -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 14230 invoked by uid 99); 30 Apr 2011 16:46:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Apr 2011 16:46:25 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sean.copenhaver@gmail.com designates 209.85.220.180 as permitted sender) Received: from [209.85.220.180] (HELO mail-vx0-f180.google.com) (209.85.220.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Apr 2011 16:46:19 +0000 Received: by vxk12 with SMTP id 12so5185805vxk.11 for ; Sat, 30 Apr 2011 09:45:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=NjQJmbZKgcj0ZVk8i965SK729LjOLqI2j33ZMaHQZVU=; b=nQxMYmEtenZzv4+zt6QI27cGlyaWygL7cxi8V0HSbMf+qy6a0d5J9QcxfzdB4peV8O 3IV023JUW4iDu0GxRb4tNjXHIitjzstkZfZdASqWU7/uxq8NvSq1d8TLuk4AxV+GSHO1 2652yoELCo4ukRSZo3C9UcedNSIP6TCU2ncsE= 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=BsHfNpoGsQ/D3eoX6CH+mgrgFOa6VB5A4ssmOdBo4ZQIY86KvwN9Xc7+djqwhFxjrY i2D1kVZ4jo1cK2rc4eZmDWfUEtUfk0oUzNQ3rwreL61cAAJRDF6dM4LG26S3+72aoTbK NKV1h1IoBap0NX4SmMzReo5uu5v+lMDQq2KN8= MIME-Version: 1.0 Received: by 10.52.76.193 with SMTP id m1mr2282064vdw.204.1304181958956; Sat, 30 Apr 2011 09:45:58 -0700 (PDT) Received: by 10.52.169.161 with HTTP; Sat, 30 Apr 2011 09:45:58 -0700 (PDT) In-Reply-To: <4DBC391D.8090806@mage.hu> References: <4DBB04C4.7070704@mage.hu> <4DBBFD2E.4080301@mage.hu> <4DBC391D.8090806@mage.hu> Date: Sat, 30 Apr 2011 12:45:58 -0400 Message-ID: Subject: Re: triggering all (necessary) view update From: Sean Copenhaver To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=bcaec501603b62d84204a2258673 --bcaec501603b62d84204a2258673 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I'm coming in late on this thread but if you want to make sure you are not blocked from querying views while they update I would suggest using the approach outlined in the wiki to write a temporary design document, then once the views are finished you write the real design document. View indexe= s are unique to design document contents, so couchdb will share the index. http://wiki.apache.org/couchdb/How_to_deploy_view_changes_in_a_live_environ= ment That paired with an external process monitoring _changes API for design document changes and I think you can basically fully automate this. On Sat, Apr 30, 2011 at 12:30 PM, Mage wrote: > Hello Jim, > > this seems to be related to triggering the view-update for the whole > database. I think it should help you too. Even with external scripting. > > Mage > > On 04/30/2011 06:08 PM, Jim Klo wrote: > > I can handle scripting the updates and eventual consistency - but I > can't handle the 2 - 5 minutes of blocking it takes for each view to upda= te > after a few thousand docs are added. > > > > - Jim > > --=20 =93The limits of language are the limits of one's world. =93 -Ludwig von Wittgenstein --bcaec501603b62d84204a2258673--