Hi, 0.5 does indeed use _changes to incrementally update the Lucene indexes; it should *not* be starting over unless you delete the index or change the index functions. 0.5 is under active development so I'm very keen to hear about this bug. I'm attempting to reproduce it locally now.
B. On Wed, Apr 14, 2010 at 11:45 AM, Manokaran K <[email protected]> wrote: > On Wed, Apr 14, 2010 at 3:58 PM, Sebastian Cohnen < > [email protected]> wrote: > >> Hi, >> >> this is (of course) not to be expected. c-l uses the _chages API and >> checkpointing (using the update sequence number) to figure out, if there is >> something new to index - at least as far as I understood this. But since 0.5 >> is not yet released, maybe you've found a bug :) Could you provide some more >> information on your setup, used design document, c-l logs? >> >> >> > My setup consists of about 150K docs to demo a web app. I'll prune it to a > much smaller number and give you the information. Any specific action you > would want me to try? > > thanks, > mano >
