Re: Re-creating IndexSearcher after update

2006-03-27 Thread Nick Atkins
archer instance is > created, some warming up is done and only then the existing one is > replaced and closeWhenDone is called on it. > > Luc > > -Original Message- > From: Koji Sekiguchi [mailto:[EMAIL PROTECTED] > Sent: dinsdag 21 maart 2006 9:24 > To: java-use

Re: Re-creating IndexSearcher after update

2006-03-21 Thread Yonik Seeley
On 3/20/06, Stephen Gray <[EMAIL PROTECTED]> wrote: > I want to re-create the IndexSearcher whenever the index changes, but I'm > assuming that if I do this bad things will happen to people who may be > currently running a search, or paging through a Hits collection created by > a previous search (

RE: Re-creating IndexSearcher after update

2006-03-21 Thread Vanlerberghe, Luc
lto:[EMAIL PROTECTED] Sent: dinsdag 21 maart 2006 9:24 To: java-user@lucene.apache.org Subject: RE: Re-creating IndexSearcher after update Hi Steve, DelayCloseIndexSearcher may suit your requirement? Please check: http://issues.apache.org/jira/browse/LUCENE-445 Hope this he

RE: Re-creating IndexSearcher after update

2006-03-21 Thread Koji Sekiguchi
Hi Steve, DelayCloseIndexSearcher may suit your requirement? Please check: http://issues.apache.org/jira/browse/LUCENE-445 Hope this helps. Koji - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [