On 19-Jun-07, at 2:48 AM, michael ravits wrote:
hi,
I am planning on reindexing from fresh on a daily basis, while
keeping the search online.
What I do is:
1. <delete><query>*:*</query></delete>
2. <add>...
3. <commit />
Works ok. But I've noticed that the faq recommends issuing
<optimize /> before reindexing. The problem is <optimize/> also
seems to commit changes, so the index is empty until I reindex and
the search can't be online.
How _not_ sending <optimize /> will affect performace/results?
Unclear; it would be best to measure it. I suspect it might not
affect performance at all. <optimize/> is mostly necessary to ensure
that certain kinds of backward-incompatible schema changes are
applied--since this implies taking down Solr anyway, you don't have
to worry about this.
Will sending <optimize /> after reindexing help?
Is there another solution?
It'll help searching but not affect indexing.
Don't worry about it unless you find that there is a performance
problem.
-Mike
