On Sun, Mar 17, 2013 at 8:19 PM, Eoghan Ó Carragáin <eoghan.ocarrag...@gmail.com> wrote: > > I can see why the Fuzzy Suggester sees "college" as a match for "colla" but > expected the exactMatchFirst parameter to ensure that suggestions beginning > with "colla" to be weighted higher than "fuzzier" matches. I > have spellcheck.onlyMorePopular set to true, in case this makes a > difference. > > Am I misunderstanding what exactMatchFirst is supposed to do? Is there a > way to ensure suggestions matching exactly what the user has entered rank > higher than fuzzy matches? >
I think exactMatchFirst is unrelated to typo-correction: it only ensures that if you type the whole suggestion exactly that the weight is completely ignored. This means if you type 'college' and there is an actual suggestion of 'college' it will be weighted above 'colleges' even if colleges has a much higher weight. On the other hand what you want (i think) is to punish the weights of suggestions that required some corrections. Currently I don't think there is any way to do that: * NOTE: This suggester does not boost suggestions that * required no edits over suggestions that did require * edits. This is a known limitation. I think the trickiest part about this is how the "punishment" formula should work. Because today this thing makes no assumptions as to how you came up with your suggestion weights... But feel free to open a JIRA issue if you have ideas !
