Hello. I'm new to Solr and would be thankful for advice for the following case: We have Suggest API running on production using Solr 6, which currently prevent changes in the response and query parameters. That's why SpellCheck component can't be used (parameter is custom, not 'q'or 'spellcheck.q'). I've tried to search for the solution, but many threads ends without any clear answer.
To my understanding there is 2 main ways. 1. Combine default filters, to emulate spellcheck behavior. Question: which combination might give good enough result? Advantage: will be very easy to integrate. Disadvantage: the quality and flexibility will be not very good 2. Implement custom filter, inside which implement advanced spellcheck functionality, using some open-source. Advantage: quality will be much higher Disadvantage: "invention of the bicycle" and even add custom filter to the production currently quite complicated. 3. Something else... open for suggestions :) The expected behavior: myrequestparam.q=iphon suggest: iphone, iphone 8... myrequestparam.q=iphonn suggest: iphone, iphone 8... If there is both cases possible and corrected suggestion is highly possible along with original one, maybe put it with lower weight in the list. But the response list should be the single entity (merged). Thanks. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
