I've got an application that will be doing constant updates to an index.
I've looked into batching those updates, however, based on the way the
application works, the updates can't be batched. (Well, I figure with a lot
of work, I might be able to batch ~10% of the transactions) Another
requiremen
java-user@lucene.apache.org
Subject: Re: Update performance/indexwriter.delete()?
Roy Klein wrote:
> So one thing I've been wondering: Why do you need to do deletes from an
> indexreader?
Is this not in the FAQ? It should be...
IndexWriter can only append documents to an index.
An
Hi Hoss,
Thanks very much for your comments.
While batch processing might work in some cases, I believe it's not "safe"
in mine.
Here's the scenario that I can't guarantee won't happen:
There might be 3 transactions in a very short time span (for example, 1
second), here's what they are:
1) up
Hi,
The "front-end" guys working on my application need a way to pass me complex
queries. I was thinking that it'd be pretty straightforward to hand them a
package which helps them to create a DOM object which describes a query
(i.e. nested Booleans combined with phrases and keyword searches, sort
