Erick said/wrote: > If you commit after docs are deleted and _still_ see them in search results, > that's a JIRA should I JIRA it?
-----Ursprüngliche Nachricht----- Von: Shawn Heisey [mailto:apa...@elyograg.org] Gesendet: Samstag, 27. Januar 2018 12:05 An: solr-user@lucene.apache.org Betreff: Re: AW: AW: SolrClient#updateByQuery? On 1/27/2018 12:49 AM, Clemens Wyss DEV wrote: > Thanks for all these (main contributor's 😉) valuable inputs! > > First thing I did was getting getting rid of "expungeDeletes". My > "single-deletion" unittest failed unti I added the optimize-param >> updateReques.setParam( "optimize", "true" ); > Does this make sense or should JIRA it? > How expensive ist this "optimization"? An optimize operation is a complete rewrite of the entire index to one segment. It will typically double the size of the index. The rewritten index will not have any documents that were deleted in it. It's slow and extremely expensive. If the index is one gigabyte, expect an optimize to take at least half an hour, possibly longer, to complete. The CPU and disk I/O are going to take a beating while the optimize is occurring. Thanks, Shawn
