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 adam.kocoloski@gmail.com
 designates 72.14.220.156 as permitted sender)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Mime-Version: 1.0 (Apple Message framework v1076)
Subject: Re: Best practice for view updates across large data sets
From: Adam Kocoloski <kocolosk@apache.org>
In-Reply-To: <a153de6d0910281209r456a803ei85c78a64c1e9246a@mail.gmail.com>
Date: Wed, 28 Oct 2009 15:40:38 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <7F79589C-7F30-4C47-A329-123252F8CA84@apache.org>
References: <9ce8c9f70910271725x2a338fcdi45ce6d55bf58d545@mail.gmail.com>
 <DC454F48-42AE-4DDC-9193-EBC623B1B6E9@apache.org>
 <a153de6d0910281209r456a803ei85c78a64c1e9246a@mail.gmail.com>
To: user@couchdb.apache.org

Hi Seggy, it's per design document.  Every time you change any view in  
a design doc, all the views in that document are reindexed.  Best,

Adam

On Oct 28, 2009, at 3:09 PM, Seggy Umboh wrote:

> That's interesting. Is the hash per design document, or per view?  
> Does it
> mean that when I change one view in my _design/development, only  
> that view
> is reindexed?
>
>
> On Tue, Oct 27, 2009 at 7:53 PM, Adam Kocoloski  
> <kocolosk@apache.org> wrote:
>
>> On Oct 27, 2009, at 8:25 PM, Larry wrote:
>>
>> As I had expected Im starting to experience lengthy re-indexing  
>> times when
>>> changing/updating our views. We have just over 300K worth of  
>>> documents
>>> currently and it will be growing. One of our views takes about 20  
>>> minutes
>>> or
>>> so to index when installed. This locks up key aspects of our  
>>> application
>>> and
>>> we would like to find a way to keep the application continuously
>>> functional.
>>> I know that our views scripts can certainly be optimized and thats
>>> something
>>> were working on as our knowledge and experience with CouchDB grows.
>>> However
>>> given where we are now I was wondering if there is a "best  
>>> practice" or
>>> any
>>> tips that users may have on updating views across large data sets.
>>>
>>> Thanks for the help!
>>>
>>> larry
>>>
>>
>> Hi Larry, one trick you may find useful in 0.10 is to take  
>> advantage of the
>> fact that the view index files are identified by the hash of their  
>> contents.
>> This means that you can have your _design/production document and  
>> your
>> _design/development document, and when you're satisfied with the  
>> dev version
>> of your app and you want to deploy it, you can just update
>> _design/production to be identical to _design/development -- your  
>> production
>> system will automatically use the prebuilt indexes from _design/ 
>> development
>> with zero downtime.  You can even use HTTP COPY to do this if you  
>> like.
>> Cheers,
>>
>> Adam
>>
>>