I could not reproduce the problem even with the two parameters you show below added to the Default handler. I tried using this default handler with different queries with correct & incorrect terms. I made sure it would sometimes successfully create collations and other times try to create collations but not find any good ones. In all cases everything worked as expected.
I also checked the code to see if possibly it could create an infinite loop whereas the queries that run to check a collation's validity were in themselves getting spell corrections back. But this doesn't look like a possibility. If you are able to figure anything more out on this yourself, then please post. If this is a real bug, then we ought to get it fixed. James Dyer E-Commerce Systems Ingram Content Group (615) 213-4311 -----Original Message----- From: O. Klein [mailto:kl...@octoweb.nl] Sent: Wednesday, July 27, 2011 9:15 AM To: solr-user@lucene.apache.org Subject: Re: Spellcheck compounded words All the talk about logging derailed the thread. So can someone test if adding <str name="spellcheck.maxCollations">2</str> <str name="spellcheck.maxCollationTries">2</str> to the dedault requesthandler in solrconfig.xml using collations causes system to hang? O. Klein wrote: > > Anyways. I was testing on 3.3 and found that when I added > &spellcheck.maxCollations=2&spellcheck.maxCollationTries=2 as parameters > to the URL there was no problem at all. > > Adding > > <str name="spellcheck.maxCollations">2</str> > <str name="spellcheck.maxCollationTries">2</str> > > to the default requestHandler in solrconfig.xml caused request to hang. > > Can someone verify if this is a bug? > -- View this message in context: http://lucene.472066.n3.nabble.com/Spellcheck-compounded-words-tp3192748p3203569.html Sent from the Solr - User mailing list archive at Nabble.com.
