lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <luc...@mikemccandless.com>
Subject Re: NewIndexModifier - - - DeletingIndexWriter
Date Thu, 08 Feb 2007 20:51:16 GMT
Doron Cohen wrote:

> Michael McCandless wrote:
> 
>> Long-ish term I think we should aim for one reader class (IndexReader)
>> that you use to do read-only things and one writer class
>> (NewIndexModifier being closest to this now) to make changes (adds,
>> deletes, optimize, etc.) to an index.
> 
> This sounds great. But at least one use case may no long be possible this
> way: there are probably applications 'out there' deleting documents in
> this logic: search the index, examine returned docs - post-processing
> them using some app-specific logic not well encapsulated in the index,
> select a few, delete them by id.

This is a very good point.  I think we must keep the deleteDocument*
methods in IndexReader around to continue to support this use case.

Mike

---------------------------------------------------------------------
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