ument while optimize() is running, so
> there's no need to protect against that. Suddenly, we're requiring every
> search application developer to disregard the documentation and think to
> himself "do I want to allow optimize() to run concurrently with
> add/deletes?&
u're ok with it, we
should document it.
I wonder though if there isn't room to introduce an atomic optimize() +
commit() in Lucene. The incentive is that optimize is not the same as
add/delete. Add/delete are operations I may want to hide from my users,
because they change the state of the i
