lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetic <otis_gospodne...@yahoo.com>
Subject Re: Exposing IndexReader commit()
Date Tue, 12 Dec 2006 02:10:20 GMT
Yeah, and that reopen, http://issues.apache.org/jira/browse/LUCENE-743, sounds very promising.
 You are right, new additions are important, too, so I am hoping for some flavour of this
reopen() that allows us to continue using the same IndexSearcher with a reopen()ed IndexReader
underneath.  As for the API, perhaps we could add:

  searcher.refresh()

Which calls Robert's IndexReader.reopen(IndexReader) underneath, and starts using the new
IndexReader transparently.

Otis

----- Original Message ----
From: Yonik Seeley <yonik@apache.org>
To: java-dev@lucene.apache.org
Sent: Monday, December 11, 2006 8:46:15 PM
Subject: Re: Exposing IndexReader commit()

On 12/11/06, robert engels <rengels@ix.netcom.com> wrote:
> I think the high-level case is that if the index is shared, you want
> the other readers to be able to see the updated deletes if they are
> notified to reread the index (using something like reopen).

It still seems like an odd usecase for one to be concerned with new
deletes but not new additions.  It *only* seems to make sense in
conjunction with reopen() functionality.

-Yonik

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





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