lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-507) Spell Checking Improvements
Date Mon, 12 May 2008 06:35:55 GMT

    [ https://issues.apache.org/jira/browse/SOLR-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595988#action_12595988
] 

Shalin Shekhar Mangar commented on SOLR-507:
--------------------------------------------

A new JIRA issue SOLR-572 is created for a Search Component for the Lucene contrib SpellChecker.

Another suggestion:
* Have a postCommit/postOptimize listener to (re)create spell checker index. Currently, the
user needs to make an explicit query to build the spell index which can be easily automated.

> Spell Checking Improvements
> ---------------------------
>
>                 Key: SOLR-507
>                 URL: https://issues.apache.org/jira/browse/SOLR-507
>             Project: Solr
>          Issue Type: New Feature
>          Components: spellchecker
>            Reporter: Jayson Minard
>
> 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:
> # 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
> # 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.
> # 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.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message