Let's be sure we're using terms similarly.... That article is from 2010, so is unreliable in the 5.2 world, I'd ignore that.
First, facets should always reflect the latest commit, regardless of expungeDeletes or optimizes/forcemerges. _commits_ are definitely recommended. Optimize/forcemerge (or expungedeletes) are rarely necessary and should _not_ be necessary for facets to not count omitted documents. Is it possible that your autowarm period is long and you're still getting an old searcher when you run your tests? Assuming that you commit(), then wait a few minutes, do you see inaccurate facets? If so, what are the exact steps you follow? Best, Erick On Tue, Dec 29, 2015 at 12:54 PM, Don Bosco Durai <bo...@apache.org> wrote: > I am purging some of my data on regular basis, but when I run a facet query, > the deleted values are still shown in the facet list. > > Seems, commit with expunge resolves this issue > (http://grokbase.com/t/lucene/solr-user/106313v302/deleted-documents-appearing-in-facet-fields > ). But it seems, commit is no more recommended. Also, I am running Solr 5.2 > in SolrCloud mode. > > What is the recommendation here? > > Thanks > > Bosco > >
