Hi,
Basically you can update/delete and read an index simultaneously.
When you start to read the index and then update/delete the index, the
current read process will continue reading with the old data before the
delete took place. A little bit like a transaction on the database.
You don't
This is generally true, most of the time.
But my experience is, there can be some FileNotFoundException, if your
searcher is opened for a while, and indexing is doing some file
deleting/renaming when merging.
Of course, if your data volumn is not that large and updating is not
often, maybe you
That shouldn't happen.
What platform(s) have you seen this on, and with what Lucene versions?
-Yonik
On 12/27/05, Chris Lu [EMAIL PROTECTED] wrote:
This is generally true, most of the time.
But my experience is, there can be some FileNotFoundException, if your
searcher is opened for a while,
If anyone could provide a testcase that can reproduce this, it would
be a huge step toward fixing it!
-Yonik
On 12/27/05, Chris Lu [EMAIL PROTECTED] wrote:
I have got around it by using two indexes, one for searching, one for
updating.
But searching FileNotFoundException lucene returns some
