>From the 3.2.0 javadocs:
"Optimize is a fairly costly operation, so you should only do it if
your search performance really requires it. Many search applications
do fine never calling optimize."
See the FAQ and javadocs on searchers and writers for thread safety info.
One thing that optimize d
I read that in a lot of cases IndexWriter.optimize does not have to be called.
I then deleted it and my junit test case broke because results were coming back
in the query that were not supposed to be coming back :(. I think everything
is single tested. Maybe I should write a more raw junit te
