Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Sat, 16 Mar 2013 18:38:13 +0000 (UTC)
From: "Erick Erickson (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12406185.1223655676843.452436.1363459093429@arcas>
In-Reply-To: <JIRA.12406185.1223655676843@arcas>
References: <JIRA.12406185.1223655676843@arcas>
Subject: [jira] [Resolved] (LUCENE-1417) Allowing for distance measures that
 incorporate frequency/popularity for SuggestWord comparison
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/LUCENE-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erick Erickson resolved LUCENE-1417.
------------------------------------

    Resolution: Won't Fix

SPRING_CLEANING_2013 we can reopen if necessary. This code is much different now
                
> Allowing for distance measures that incorporate frequency/popularity for SuggestWord comparison
> -----------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-1417
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1417
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/spellchecker
>    Affects Versions: 2.4
>            Reporter: Jason Rennie
>            Priority: Minor
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Spelling suggestions are currently ordered first by a string edit distance measure, then by popularity/frequency.  This limits the ability of popularity/frequency to affect suggestions.  I think it would be better for the distance measure to accept popularity/frequency as an argument and provide a distance/score that incorporates any popularity/frequency considerations.  I.e. change StringDistance.getDistance to accept an additional argument: frequency of the potential suggestion.
> The new SuggestWord.compareTo function would only order by score.  We could achieve the existing behavior by adding a small inverse frequency value to the distances.

--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org