On Tue, Dec 6, 2011 at 5:04 PM, Scott Smith <ssm...@mainstreamdata.com> wrote: > If I read the 3.5 lucene javadocs, optimize() has been deprecated because it > is "rarely justified" with the current lucene index implementation
It's functionality is not being deprecated... it's just that the method is being renamed in Lucene (it's staying as "optimize" in solr). Using optimize is all about tradeoffs... it's expensive since it rewrites the complete index (i.e. forces a merge of all segments into one). People interested in near-realtime indexing on large indexes should definitely avoid optimizing. If index changes don't need to be visible as often, or for smaller indexes like yours, it really depends on what you are optimizing for... memory use, query throughput, indexing bandwidth, turnaround-time (i.e. near-realtime), etc. -Yonik http://www.lucidimagination.com
