[
https://issues.apache.org/jira/browse/LUCENE-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3846:
--------------------------------
Attachment: LUCENE-3846_fuzzy_analyzing.patch
here's my hacky Fuzzy+Analyzing prototype.
But we need to fix intersectPrefixPaths to be able to efficiently intersect
transition ranges (e.g. findTargetArc + readNextArc through the range?).
anyway we should see how slow this is compared to mike's: the advantage would
be you would still get all the stuff AnalyzingSuggester has...
> Fuzzy suggester
> ---------------
>
> Key: LUCENE-3846
> URL: https://issues.apache.org/jira/browse/LUCENE-3846
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 4.1
>
> Attachments: LUCENE-3846_fuzzy_analyzing.patch, LUCENE-3846.patch,
> LUCENE-3846.patch
>
>
> Would be nice to have a suggester that can handle some fuzziness (like spell
> correction) so that it's able to suggest completions that are "near" what you
> typed.
> As a first go at this, I implemented 1T (ie up to 1 edit, including a
> transposition), except the first letter must be correct.
> But there is a penalty, ie, the "corrected" suggestion needs to have a much
> higher freq than the "exact match" suggestion before it can compete.
> Still tons of nocommits, and somehow we should merge this / make it work with
> analyzing suggester too (LUCENE-3842).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
