[jira] Commented: (SOLR-485) Deprecate SpellCheckRequestHandler replace with one that does query analysis and spell checks each token

["Ryan McKinley (JIRA)" <ji...@apache.org>]

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

Ryan McKinley commented on SOLR-485:
------------------------------------

Is the concern here not to break compatibility for folks who use are using the /trunk SCRH?

Before releasing 1.3, we _could_ consider reverting SCRH to the 1.2 version -- this way we have less code to maintain.  As we move forward, are new features added to both?  

(I'm fine keeping it in... just want to make sure we consider it before 1.3 release)

> Deprecate SpellCheckRequestHandler replace with one that does query analysis and spell checks each token
> --------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-485
>                 URL: https://issues.apache.org/jira/browse/SOLR-485
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 1.2
>            Reporter: Grant Ingersoll
>            Assignee: Grant Ingersoll
>            Priority: Minor
>             Fix For: 1.3
>
>
> The current spellchecker does not handle multiword queries very well, if at all.  Depending on the settings, it either ignores multiword tokens, or it splits on whitespace.  It should use the query analyzer associated with the spelling field to produce tokens for spelling.
> We should deprecate the current one and replace it with one that is similar, but does the appropriate thing with the query tokens.
> Seehttp://www.mail-archive.com/solr-dev@lucene.apache.org/msg07542.html

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