[
https://issues.apache.org/jira/browse/SOLR-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572890#action_12572890
]
Grant Ingersoll commented on SOLR-485:
--------------------------------------
I suppose that depends on whether you think people should still use the
existing one. My take is it should be, since it doesn't analyze the tokens,
thus things like case, etc. and it can't even take in multiword queries, which
would be pretty common. Essentially, it really forces you to do things on the
client side that shouldn't need to be done.
Ideally, the new version is a search component, such that one doesn't have to
send separate requests, either.
> 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.
