On Mon, May 27, 2013 at 7:11 AM, Jack Krupansky <j...@basetechnology.com> wrote: > The intent is that optimize is obsolete and should no longer be used
That's incorrect. People need to understand the cost of optimize, and that it's use is optional. It's up to the developer to figure out of the benefits of calling optimize outweigh the costs in their particular situations. The wiki currently says: """ An optimize is like a hard commit except that it forces all of the index segments to be merged into a single segment first. Depending on the use cases, this operation should be performed infrequently (like nightly), if at all, since it is very expensive and involves reading and re-writing the entire index. Segments are normally merged over time anyway (as determined by the merge policy), and optimize just forces these merges to occur immediately. """ -Yonik http://lucidworks.com
