couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Manokaran K <>
Subject Re: couchdb-lucene reindexes when restarted
Date Fri, 16 Apr 2010 09:20:16 GMT
On Fri, Apr 16, 2010 at 1:51 PM, Robert Newson <>wrote:

> That's more interesting. IIRC, Lucene's commit() method will only
> write to disk if there have been document changes. So, if your
> function doesn't update anything at all (your function returns null
> for all documents, say) then the update_seq won't be updated, and
> hence it will start over each time.

I think you have got it!

I tested the above by creating another doc (after all the others have been
generated by the ruby script) that will ensure that at least one _fti index
function will return a value. Now, its working as expected - the update_seq
got bumped to the latest and survives restarts!!

But am curious: would it not be better if lucene bumped up the seq number
every time it indexed whether or not the index functions returned a value!

thanks a ton for your efforts.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message