The picture didn't come through to the list.
If you are really fully re-indexing and replacing the index every time
then you should just open a new IndexReader instead of trying to
.maybeReopen? Ie, the newly opened reader cannot share any segments
with the old one, so you get no benefit from it.
We are not copying index files from one index to another. Will try to explain:
1 - We have a unix script that removes the old physical index and create a new
one several times a day from the database.
2 - The SearcherManager call maybeReopen in a separate thread from the main
application every f
It sounds like you are somehow copying over index files from one index to
another?
You shouldn't do that; use IW.addIndexes instead.
Or maybe give a bigger picture of how your application works with Lucene?
Mike McCandless
http://blog.mikemccandless.com
On Wed, Nov 6, 2013 at 6:46 PM, Alexei
Hi guys,
I have a question about a problem we had with the SearcherManager.maybeReopen()
method. This works as charm except when the segments in the previous index has
the exact same names as the segments in the new one. In this case the
maybeReopen() doesn't load the new index, even though the
Hi guys,
I have a question about a problem we had with the SearcherManager.maybeReopen()
method. This works as charm except when the segments in the previous index has
the exact same names as the segments in the new one. In this case the
maybeReopen() doesn't load the new index, even though the
Hi guys,
I have a question about a problem we had with the SearcherManager.maybeReopen()
method. This works as charm except when the segments in the previous index has
the exact same names as the segments in the new one. In this case the
maybeReopen() doesn't load the new index, even though t
