It only rebuilds on explicit optimize operations. A background merge that merges all segments (to 1) won't fire the rebuild AFAIK.
And Upayavira is right, you can choose to use a DirectSolrSpellChecker, that way you don't need an external index at all. On Mon, Dec 17, 2012 at 9:46 AM, Upayavira <u...@odoko.co.uk> wrote: > Note with 4.0 you don't need to build a spellcheck index. Spellchecking > can happen from your main index (unless you are providing your own > dictionary). > > Upayavira > > On Mon, Dec 17, 2012, at 12:36 PM, Artyom wrote: > > Thank you, Tomás. > > > > This wiki > > > http://wiki.apache.org/solr/UpdateXmlMessages#A.22commit.22_and_.22optimize.22 > > says > > "*Segments are normally merged over time anyway (as determined by the > > merge > > policy), and optimize just forces these merges to occur immediately.*" > > > > Doesn't the merge policy affects buildOnOptimize setting and trigger > > spellcheck index rebuilding? > > > > > > > > -- > > View this message in context: > > > http://lucene.472066.n3.nabble.com/SolrCloud-with-Near-Realtime-Search-buildOnOptimize-in-IndexBasedSpellChecker-tp4027499p4027510.html > > Sent from the Solr - User mailing list archive at Nabble.com. >
