[
https://issues.apache.org/jira/browse/SOLR-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595973#action_12595973
]
Shalin Shekhar Mangar commented on SOLR-485:
--------------------------------------------
Otis - I was being careful not to break compatibility with current clients but
I also think it makes sense to implement this as a Search Component from the
ground up. Existing clients can continue to use SCRH and new clients can use
the search component. That way, we can provide all the latest and greatest
features without resorting to unintuitive syntax that may be needed to remain
backwards-compatible.
> 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.
