[
https://issues.apache.org/jira/browse/LUCENE-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916883#action_12916883
]
Robert Muir commented on LUCENE-2507:
-------------------------------------
I'll work on cleaning up tests and doc, i think we can then commit this with
the functionality it has.
bq. It's great that it leverages the absurd speedups we've made to FuzzyQuery
in 4.0.
Yes, if you read that scary fuzzy paper it seems thats its original use-case
all along (we just did FuzzyQuery first, and re-used it here):
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.16.652
Along the same lines, I think we can then later improve both spellcheckers in
easy ways. For example,
it would be good to add a concept of "SpellCheckFilter" that can return
true/false if a word is correctly spelled.
Docfreq-based stuff helps, but if you know the language, something like
hunspell could go a long way here
to both preventing either spellchecker from trying to correct an
already-correctly-spelled word or preventing
it from suggesting misspellings.
> automaton spellchecker
> ----------------------
>
> Key: LUCENE-2507
> URL: https://issues.apache.org/jira/browse/LUCENE-2507
> Project: Lucene - Java
> Issue Type: New Feature
> Components: contrib/spellchecker
> Reporter: Robert Muir
> Assignee: Robert Muir
> Fix For: 4.0
>
> Attachments: LUCENE-2507.patch, LUCENE-2507.patch, LUCENE-2507.patch,
> LUCENE-2507.patch
>
>
> The current spellchecker makes an n-gram index of your terms, and queries
> this for spellchecking.
> The terms that come back from the n-gram query are then re-ranked by an
> algorithm such as Levenshtein.
> Alternatively, we could just do a levenshtein query directly against the
> index, then we wouldn't need
> a separate index to rebuild.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]