couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roger Binns <>
Subject Re: filters for _changes dont seem to work
Date Sat, 28 Nov 2009 21:53:28 GMT
Hash: SHA1

Sven Helmberger wrote:
> You are not writing back documents with the same content, are you?

In my case, no.  For my testing it is documents being created and destroyed
which aren't been noticed by filter after they initially are.

Robert Dionne wrote:
> I just happened to be looking at the code that handles this and am
> wondering if it's a timing issue. Could you try increasing the timeout
> or not specifying it (the default looks to be 60s) and/or setting
> delayed_commits to false in the config file.
> I could be that the code that runs the filters is not getting the
> notifications in time. I"m just speculating but it's an easy test to try.

Changing delayed_commits to false did not make a difference.  The timeout
just sets the maximum amount of time before the http response completes.  If
not specified it is 60 seconds, works as expected when set to 10 seconds and
when set to lots of 9's behaved as though it was set to 60 seconds.  I am
using heartbeat which works as documented.

While looking at that code something that would be very nice is if the http
response does not complete until there is at least one change *after* the
filter has been applied (or a timeout etc).  Currently the response
completes if there is at least one change before the filter - I have the
filter because I only care about .1% of my documents changing (filter on

Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


View raw message