[
https://issues.apache.org/jira/browse/SOLR-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597917#action_12597917
]
Shalin Shekhar Mangar commented on SOLR-572:
--------------------------------------------
Bojan -- I don't want to hold you up so I've uploaded the current state of my
work. Please go ahead with your changes. I can continue after you're done.
Another issue I noticed with the SCRH is that it accepts the accuracy as a
request parameter and calls Lucene SpellChecker.setAccuracy before getting the
suggestion. However, this is neither thread-safe nor can we guarantee that the
accuracy is actually enforced for the suggestion. Therefore, I think we should
only have accuracy configurable in the solrconfig.xml and not as a request
parameter.
> Spell Checker as a Search Component
> -----------------------------------
>
> Key: SOLR-572
> URL: https://issues.apache.org/jira/browse/SOLR-572
> Project: Solr
> Issue Type: New Feature
> Components: spellchecker
> Affects Versions: 1.3
> Reporter: Shalin Shekhar Mangar
> Fix For: 1.3
>
> Attachments: SOLR-572.patch, SOLR-572.patch, SOLR-572.patch
>
>
> Expose the Lucene contrib SpellChecker as a Search Component. Provide the
> following features:
> * Allow creating a spell index on a given field and make it possible to have
> multiple spell indices -- one for each field
> * Give suggestions on a per-field basis
> * Given a multi-word query, give only one consistent suggestion
> * Process the query with the same analyzer specified for the source field and
> process each token separately
> * Allow the user to specify minimum length for a token (optional)
> Consistency criteria for a multi-word query can consist of the following:
> * Preserve the correct words in the original query as it is
> * Never give duplicate words in a suggestion
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
