Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of cameron@datashovel.com
 designates 209.85.214.173 as permitted sender)
Message-ID: <520E4665.4070003@datashovel.com>
Date: Fri, 16 Aug 2013 11:33:57 -0400
From: Cameron Jacobson <cameron@datashovel.com>
Reply-To: cameron@datashovel.com
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: best way to "warm" views offline
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

What is the best way to "warm" views offline?  Also, if possible, can
you explain the mechanics that CouchDB uses in order to "know" that a
given view is or isn't new?  In other words, when deploying an updated
design document how would the server go about determining whether a
given view within that design document is different or not?  Is it
through hashing?  Or do all views within the design document require a
pre-deployment query?

None of my datasets have ever really been big enough to required offline
prepping of views, but I'm anticipating this will change soon so I want
to make sure I'm using best practices when I'm ready to make this change
to my deployment process.

Thanks