lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Beard, Brian" <Brian.Be...@mybir.com>
Subject RE: MultiSearcher holds on to index - optimization not one segment
Date Tue, 19 Jun 2007 13:49:33 GMT
This may seem like a naïve question - since the garbage collection is not enforcable, is it
possible to send a flag to the IndexReader to give this up once the reader is no longer needed?

-----Original Message-----
From: yseeley@gmail.com [mailto:yseeley@gmail.com] On Behalf Of Yonik Seeley
Sent: Tuesday, June 19, 2007 9:06 AM
To: java-user@lucene.apache.org
Subject: Re: MultiSearcher holds on to index - optimization not one segment

On 6/19/07, Beard, Brian <Brian.Beard@mybir.com> wrote:
> The problem I'm having is once the MultiSearcher is open, it holds on to
> the index file

An IndexReader holds open the files... this is a feature.  Not holding
the file open would mean that the index would actively change while
being searched.  Lucene is designed to search on a static index (but
one that can be updated in the background with no impact to the
current open readers).

-Yonik

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




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


Mime
View raw message