Not explict closing can lead especially when is allowed a lot of memory
to JVM but small amount is used that old files will stay on the disk on
linux.
Solution is in using ReentrantReadWriteLock
where the re-open method opens new indexreader at ThreadLocal
accuire write lock
saves old reference
-
From: Mike Streeton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 06, 2006 4:02 AM
To: java-user@lucene.apache.org
Subject: RE: spring & lucene
We wrote ours for NetSearch to handle this specific issue. I suggest you
create a holder class to hold the IndexReader and IndexSearcher, this
-
From: Rajiv Roopan [mailto:[EMAIL PROTECTED]
Sent: 06 June 2006 05:28
To: java-user@lucene.apache.org
Subject: spring & lucene
Hello,
I'm using the spring framework to define my indexsearcher and
indexwriter. They are defined as persistent singletons in the
application.
I'm quite
Hi,
when working with Spring, the best is to use Compass :
http://www.opensymphony.com/compass/ (if you can).
Regards,
Sami Dalouche
On Tue, 2006-06-06 at 00:27 -0400, Rajiv Roopan wrote:
> Hello,
> I'm using the spring framework to define my indexsearcher and
> indexwriter. They are defined
Hello,
I'm using the spring framework to define my indexsearcher and
indexwriter. They are defined as persistent singletons in the
application.
I'm quite new to lucene and I realize that after updating an index
using IndexWriter you nead to re-create an instance of IndexSearcher
to search that
