Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4D3DDA42.1040807@ianhobson.co.uk>
Date: Mon, 24 Jan 2011 20:00:02 +0000
From: Ian Hobson <ian@ianhobson.co.uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB;
 rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Mnenhy/0.8.3 Thunderbird/3.1.7
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Re: Using the API to tell if a compact has been done
References: <4D3DBBBE.30902@databill.com>
In-Reply-To: <4D3DBBBE.30902@databill.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 24/01/2011 17:49, Wayne Conrad wrote:
> I've subscribed again, from another email address, because the list 
> decided that my first subscribtion was a eeeeevil spammer.  I hope 
> that's OK.  Anyhow...
>
> I've written a cron job that periodically compacts all databases on 
> all servers, but it needs an automated test, and an automated test 
> needs a way to know that compaction happend (or, at least, was 
> triggered).  Other than seeing the file size change, is there anything 
> I can do from the API that will show that my cron job caused 
> compaction to happen?
>
Hi Wayne,

If you can create the database you are to compact, then you can use the 
rev=??? parameter.

Set up the database, and note the rev of a document  (= oldrev)
Update the document (creating _rev=newrev). oldrev is now on disk, but 
not normally available.

Read the old version using the rev=oldrev parameter.

Trigger the compaction and wait for it to finish (A 1 record database 
won't take long to compact :) )

Read the old record again. This time it won't be found if the compaction 
has run.

See 
http://wiki.apache.org/couchdb/HTTP_Document_API#Accessing_Previous_Revisions 


Regards

Ian