That works, thanks.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yonik Seeley
Sent: Tuesday, June 19, 2007 9:57 AM
To: java-user@lucene.apache.org
Subject: Re: MultiSearcher holds on to index - optimization not one segment
On 6/19/07, Beard, Brian
On 6/19/07, Beard, Brian <[EMAIL PROTECTED]> wrote:
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?
You call close() on the IndexReader (or the IndexSear
: 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 <[EMAIL PROTECTED]> wrote:
> The problem I'm having is once the MultiSearcher is open, it holds on to
> t
On 6/19/07, Beard, Brian <[EMAIL PROTECTED]> 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.
