Hi Klaus,
If you've really still got 500MB of changes to your index since the last
time you commit()'ed, then the call to commit() will be costly and take a
while to complete. If in another thread, you reopen() an IndexReader
pointing to that index, it will only see changes since the most recen
It depends on whether or not the commit completes before the
reopen. Lucene 2.9 adds an IndexWriter.getReader method that
will always return with the latest modifications to your index.
So if you're adding many documents, you can at anytime, call
IW.getReader and you will be able to search the cha
Hi,
I've read that it is possible to update the index while another thread has a
reader open.
Now let's say the reader is trying to reopen the index (using its reopen
method) and at the very same time, the write its committing its 500MB changes
to the index. My question is, what happens in th
Hi,
I did a quick google search and couldn't find any info on this...
I seem to be having a problem when I try to execute a search using a
HitCollector while the index is being indexed. Does it make sense that I
could be getting this error because the index is being merged while the
HitCollector i
Hi,
I did a quick google search and couldn't find any info on this...
I seem to be having a problem when I try to execute a search using a
HitCollector while the index is being indexed. Does it make sense that I
could be getting this error because the index is being merged while the
HitCollector i
