no, you didn't miss anything. The comment at Lucen Revolution was more along the lines that optimize didn't actually improve much #absent# deletes.
Plus, on a significant size corpus, the doc frequencies won't changed that much by deleting documents, but that's a case-by-case thing Best Erick On Thu, Nov 4, 2010 at 4:31 PM, Markus Jelsma <markus.jel...@openindex.io>wrote: > Huh? That's something new for me. Optmize removed documents that have been > flagged for deletion. For relevancy it's important those are removed > because > document frequencies are not updated for deletes. > > Did i miss something? > > > For what it's worth, the Solr class instructor at the Lucene Revolution > > conference recommended *against* optimizing, and instead suggested to > just > > let the merge factor do it's job. > > > > On Thu, Nov 4, 2010 at 2:55 PM, Shawn Heisey <s...@elyograg.org> wrote: > > > On 11/4/2010 7:22 AM, stockiii wrote: > > >> how can i start an optimize by using DIH, but NOT after an delta- or > > >> full-import ? > > > > > > I'm not aware of a way to do this with DIH, though there might be > > > something I'm not aware of. You can do it with an HTTP POST. Here's > > > how to do it with curl: > > > > > > /usr/bin/curl "http://HOST:PORT/solr/CORE/update"; \ > > > -H "Content-Type: text/xml" \ > > > --data-binary '<optimize waitFlush="true" waitSearcher="true"/>' > > > > > > Shawn >
