[SOLR-507] Spell Checking Improvements

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: spellchecker
• Assignee: Unassigned
• Reporter: Jayson Minard
• Created: 18/Mar/08 21:45
• Updated: 18/Aug/10 14:08
• Resolved: 09/Aug/10 15:07

Description

Creating a placeholder issue to track Spell Checking Improvements. Individual issues can later be created and linked for each area of separable concern when they are determined.

Areas to discuss include:

1. spell suggestions from within the current query (minus terms being corrected) and filter so that suggestions are always valid
   • need approaches to merging the spelling list with the current mask of valid records. Also, is this a better change to Lucene first, or something that belongs in Solr?
   • need to add spell checking as query component and make available to various query handlers
   • spell checking to be field specific to support responding correctly with dismax queries
2. spell suggestions from a distributed search (SOLR-303) by augmenting the response, or alternatively just provide a federating of Spell Checker requests on their own and let the application decide when to use each.
3. spell suggestions as a search component to augment other queries

What are other typical areas of concern, or suggestions for improvements for spell checking that can be tracked?

I am willing to look at driving a patch for this area, especially for spell checking working within the current result set, and across distributed search.

Issue Links

• incorporates: SOLR-572 Spell Checker as a Search Component
• is related to: LUCENE-2608 Allow for specification of spell checker accuracy when calling suggestSimilar
• relates to: SOLR-303 Distributed Search over HTTP
• relates to: SOLR-2010 Improvements to SpellCheckComponent Collate functionality
• relates to: LUCENE-2479 need the ability to also sort SpellCheck results by freq, instead of just by Edit Distance+freq
• relates to: SOLR-785 Distributed SpellCheckComponent