Check to see if index is optimized

2005-01-07 Thread Crump, Michael
Hello, Lucene is great! I just have a question. Is there a simple way to check and see if an index is already optimized? What happens if optimize is called on an already optimized index - does the call basically do a noop? Or is it still and expensive call? Regards, Michael

RE: Problems with Lucene + BDB (Berkeley DB) integration

2004-09-21 Thread Crump, Michael
Try setUseCompoundFile(false) on your IndexWriter as soon as you create it or before you call optimize -Original Message- From: Christian Rodriguez [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 21, 2004 1:10 PM To: Lucene Users List Subject: Re: Problems with Lucene + BDB (Berkeley

RE: problem with locks when updating the data of a previous stored document

2004-09-16 Thread Crump, Michael
You have to close the IndexReader after doing the delete, before opening the IndexWriter for the addition. See information at this link: http://wiki.apache.org/jakarta-lucene/UpdatingAnIndex Regards, Michael -Original Message- From: Paul Williams [mailto:[EMAIL PROTECTED] Sent:

continuous index updates

2004-08-20 Thread Crump, Michael
Hello, I am currently working on a server app that will require the ability to make index additions/deletions at any time. I want to cache/reuse index searchers and readers. I know that once an index has changed only newly opened readers will see the changes. Creating a new reader to see

RE: continuous index updates

2004-08-20 Thread Crump, Michael
IndexSearcher alone, and JVM's garbage collection cleans it up. Otis --- Crump, Michael [EMAIL PROTECTED] wrote: Hello, I am currently working on a server app that will require the ability to make index additions/deletions at any time. I want to cache/reuse index searchers and readers. I