How important is closing an IndexSearcher/IndexModifier on application exit?

2006-11-29 Thread Eric Brown
I'm the only application accessing my index. Is there any chance the lucene index might remain in a locked state if I don't call close() my IndexSearcher or IndexModifier on applicaiton exit? I'm several layers down in a webapp, so using Runtime.addShutdownHook () is unreliable if my webapp

Cached Hits / closing IndexSearcher after add/delete w/IndexModifier

2006-11-29 Thread Eric Brown
I'm using lucene as a backend for my webservices that provide add, remove and search operations. When I add or remove documents via IndexModifier, I believe I'm supposed to close the IndexSearcher I use for query requests. However, I cache Hits and I believe the javadocs indicate closing an

Re: Cached Hits / closing IndexSearcher after add/delete w/IndexModifier

2006-11-29 Thread Eric Brown
Hi Yonik, On Nov 29, 2006, at 11:16 AM, Yonik Seeley wrote: On 11/29/06, Eric Brown <[EMAIL PROTECTED]> wrote: [snip] Also, should I keep one IndexModifier open for the life of my service/ application or should I open and close it when I get new requests to add or remove documents? (I