You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Sascha Szott (JIRA)" <ji...@apache.org> on 2019/02/28 22:23:00 UTC
[jira] [Commented] (LUCENE-4500) Loosen up DirectSpellChecker's
minPrefix requirements
[ https://issues.apache.org/jira/browse/LUCENE-4500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780981#comment-16780981 ]
Sascha Szott commented on LUCENE-4500:
--------------------------------------
Should we at least add a short note to the reference guide that explains the effect of setting *minPrefix* effectively to 1 (even if the user set it to 0) in case no suggestions with an edit distance of 1 are available in the dictionary?
> Loosen up DirectSpellChecker's minPrefix requirements
> -----------------------------------------------------
>
> Key: LUCENE-4500
> URL: https://issues.apache.org/jira/browse/LUCENE-4500
> Project: Lucene - Core
> Issue Type: Improvement
> Affects Versions: 4.0
> Reporter: Erik Hatcher
> Priority: Minor
>
> DirectSpellChecker currently mandates a minPrefix of 1 when editDistance=2. This prohibits a query of "nusglasses" from matching the indexed "sunglasses" term.
> Granted, there can be performance issues with using a minPrefix of 0, but it's a risk that a user should be allowed to take if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org