One thing you could do is index your entire spell check file into lucene as string values. That way your index will be available across the cloud and you can build your dictionary from the indexed field. This will however mean that everytime you change the spellcheck file, you will need to do reindexing. If your number of updates to this dictionary file are small, you can simply write a routine that will use atomic updates to update your index directly and save you the trouble of doing a full reindex.
On Wed, Jan 20, 2016 at 8:47 PM Riyaz <shaik.ri...@viacomcontractor.com> wrote: > Hi, > > *Environment: * > Solr-4.10.4 > tomcat6 > Solr Cloud - 6 shards and 6 replicas with external zookeeper ensemble > > We are configuring Filebased spellcheck component on Solr Cloud. The source > file for dictionary generation having 5 million text entries. Since the > solr > configurations(including spellings_xxx.txt) are distributed by zookeeper to > all the nodes in the cloud. Is it built the spellcheck dictionary on all > the > leaders/replicas using same source file?. Can you please share is there any > better way to configure the same?. > > The source file(spellings_xxx.txt) will be changed frequently and have to > build the spellcheck dictionary accordingly. > > Thanks > Riyaz > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/FileBased-Spellcheck-on-Solr-cloud-tp4252034.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- Regards, Binoy Dalal
