On Tue, Apr 03, 2007 at 08:31:20AM -0400, Michael McCandless said:
> Optimize actually does its own flush before optimizing, so you don't
> need to call it yourself and in fact calling it after optimize will
> just be a harmless no-op.
Ah, that's good to know.
> You should be worried about this
"Simon Wistow" <[EMAIL PROTECTED]> wrote:
> I have an Indexer which inserts tasks onto a queue and then has a thread
> which consumes the tasks (Index, Update or Delete) and executes them. If
> the Indexer is shut down it stops the thread, waits until it's finished
> its current task and then co
I have an Indexer which inserts tasks onto a queue and then has a thread
which consumes the tasks (Index, Update or Delete) and executes them. If
the Indexer is shut down it stops the thread, waits until it's finished
its current task and then consumes any other tasks on the queue. Then it
runs
