lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antony Bowesman <...@teamware.com>
Subject Re: IndexWriter shutdown
Date Tue, 22 May 2007 05:26:13 GMT
Doron Cohen wrote:
> Antony Bowesman wrote:
>> Another use this may have is that mini-optimize operations could be
>> done at more
>> regular intervals to reduce the time for a full optimize.  I could
>> then schedule
>> mini-optimise to run for a couple of minutes at more frequent intervals.
> 
> This seems to assume the proposed feature allows to continue an
> interrupted merge at a later time, from where it was stopped. But
> if I understood correctly then the proposed feature does not work
> this way - so all the (uncommitted) work done until shutdown will
> be "lost" - i.e. next merge() would start from scratch.

Yes, it does (wrongly) assume that.  For some reason, I had thought the optimize 
operation was a copy+pack operation, but of course, it's not, so I can see why 
this incremental approach is not possible (or at least non trivial).

Still, the shutdown function would be useful on its own.
Antony




---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message