slubow...@netzero.net wrote:
I am trying to use a simple filter to filter the changes I get when asking for changes using the _changes API.
I find that often the filter is not even called (I write a message to the log when the filter is called, when it returns false, and when it returns true)
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
Hi,
i don't know what i'm missing - maybe someone can push me in the right
direction?
I installed couchdb-lucene 0.4 and couchdb seems to start without errors.
I created a document:
{
_id: _design/lucene,
_rev: 2-f7d29646a16db961903f7d7b73fe1d77,
fulltext: {
by_name: {
Verify that you've hooked up the indexer (under update_notification)
and verify that it has built indexes (you should find a directory
called 'lucene').
Also check both the couchdb.log and couchdb-lucene.log for errors.
B.
On Sat, Nov 28, 2009 at 1:38 PM, Smrchy smr...@gmail.com wrote:
Hi,
i
I've got a lucene directory that contains some files but they are really
small, so it seems not much was indexed. There are no errors in the
couchdb-lucene.log and i get this in my couch.log (in debug mode):
[Sat, 28 Nov 2009 14:27:46 GMT] [info] [0.1.0] Apache CouchDB has started
on
-BEGIN PGP SIGNED MESSAGE-
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:
