Anuvenk, I may be partially wrong on my prior statement.
I created that JavaDoc comment as part of my work on the spellcheck handler so I might have been wrong about it being 100% superseded. There is a chance that although the code was changed, the JavaDocs were not updated (they are merely comments in the source code). Off hand I cannot comment on what has changed since my work load at work has shifted and I have yet to implement a spell checker within the project that needs it (a biomedical project focused on genetic based diseases, so hence the medical terms in the JavaDocs). But I think I recall reviewing the daily builds a few months ago that not only has the parameters been altered (for the better I think), but also the structure of the generated XML. Originally, the purpose of "multiWords" was to internally break a multi word string in to individual components and have each component checked individually, as what you were expecting and hence your confusion if it is no longer supported. So, I am sorry for any confusion but I don't know the current status of the handler. Best of luck! Scott Tabar ---- anuvenk <[EMAIL PROTECTED]> wrote: Thanks. But i'm looking at this http://.../spellchecker?indent=on&onlyMorePopular=true&accuracy=.6&suggestionCount=20&q=facial+salophosphoprotein on http://lucene.apache.org/solr/api/org/apache/solr/handler/SpellCheckerRequestHandler.html It seems to return results (well in the example) with and without extendedResults=true does it mean that 'facial salophosphoprotein' was a single term in the index. hossman wrote: > > : > : I did try with the latest nightly build and followed the steps outlined > in > : http://wiki.apache.org/solr/SpellCheckerRequestHandler > : with regards to creating new catchall field 'spell' of type 'spell' and > : copied my text fields to 'spell' at index time. > : Still q=grapics returns 'graphics' > : but q=grapics card returns nothing. > : But the same queries return the correct spelling with string fieldtypes. > : Any fix available? > > I don't think Otis was suggesting any specific fix was available in the > nightly builds, i believe he was just addressing specificly that if there > was a bug someone commited a fix for you didnt' need to wait for 1.3 -- > you can test it now using the nightly builds. > > That said: I don't see any currently open or recent resolved bugs > related to spellchecking and multiple words ... i believe (but i'm not > 100% positive) that "multi word" spell correction will work, as long as > your dictionary contaisn those "multiple words" as individual "terms" > > ie: if you want "graphics card" to be a suggestion for "grapics card" then > you need to use a termSourceField in which "graphics card" is a single > term (either because it is untokenized, or maybe because you use a > word-based ngram tokenfilter, etc...) > > alternately, if you want to get "graphics asdfghjk" as a suggestion for > "grapics asdfghjk" (even though "asdfghjk" isn't in your index at all), > hiting the spellcorrection handler for each input word individually is > probably your best bet. > > > : > You don't need to wait for 1.3 to be released - you can simply use a > : > recent nightly build. > > > -Hoss > > > -- View this message in context: http://www.nabble.com/spellcheckhandler-tp14627712p15100704.html Sent from the Solr - User mailing list archive at Nabble.com.
