Ok, you've got me! ;)
How do you assure that your IndexModifier (or IndexWriter/IndexReader)
is closed, when your application ends.
Or do you always use a IndexReader.unlock(Directory dir) at startup-time of
your application.
Thanks!
lude
On 8/21/06, Simon Willnauer <[EMAIL PROTECTED]> wrote:
In GDataServer I use a timed indexer who commits the modifications
after a certain idle time or after n documents insert/update/delete.
This ensures that your modifications will be available after a defined
time. it also minimize opening and closing readers and writers as the
deletes will be done
my only caution is that as your index grows, the close/open of your readers
may take more time than you are willing to spend. Not that I'm recommending
against it as I don't know the details, but it's something to keep an eye
on. In my experience, "immediately available" may really mean "available
Thanks simon.
In practice my application would have around 100 queries and around 10
add/deletes per minute.
Add/deletes should show up immediately.
That means that I should always create and close an IndexModifier (and
IndexReader for Searching) for each operation, right?
Sure, it cost's a litt
On 8/20/06, lude <[EMAIL PROTECTED]> wrote:
Hello,
when using the new IndexModifier of Lucene 2.0, what would be
the best creation-pattern?
Should there be one IndexModifier instance in the application (==singelton)?
Could an IndexModifier be opened for a longer time or should it be created
on
