Did you have a specific reason why you didn't want to send an HTTP request to Solr to perform the spellcheck operation? I mean, that is probably easier than diving into raw Lucene code. Also, Solr lets you do a spellcheck from a remote client whereas the Lucene spellcheck needs to be on the same machine as the Lucene/Solr index directory.
-- Jack Krupansky On Fri, Oct 2, 2015 at 7:42 AM, Mark Fenbers <mark.fenb...@noaa.gov> wrote: > Thanks for the suggestion, but I've looked at aspell and hunspell and > neither provide a native Java API. Further, I already use Solr for a > search engine, too, so why not stick with this infrastructure for spelling, > too? I think it will work well for me once I figure out the right > configuration to get it to do what I want it to. > > Mark > > > On 10/1/2015 4:16 PM, Walter Underwood wrote: > >> If you want a spell checker, don’t use a search engine. Use a spell >> checker. Something like aspell (http://aspell.net/ <http://aspell.net/>) >> will be faster and better than Solr. >> >> wunder >> Walter Underwood >> wun...@wunderwood.org >> http://observer.wunderwood.org/ (my blog) >> >> >> >
