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

Oleg Gnatovskiy commented on SOLR-572:
--------------------------------------

Hey guys. Installed the latest patch. Old problem is still there. For example 
if I do q=pizzzzza I get:

<lst name="spellcheck">

        <lst name="suggestions">

        <lst name="pizzza">
<int name="numFound">1</int>
<int name="startOffset">0</int>
<int name="endOffset">6</int>

        <arr name="suggestion">
<str>pizza</str>
</arr>
</lst>
</lst>
</lst>

Which is good. Then I do q=pizza (pizza is in the dictionary)

lst name="spellcheck">

        <lst name="suggestions">

        <lst name="pizza">
<int name="numFound">1</int>
<int name="startOffset">0</int>
<int name="endOffset">5</int>

        <arr name="suggestion">
<str>plaza</str>
</arr>
</lst>
</lst>
</lst>

I don't think it should give me that suggestion. If a word is in the dictionary 
it should not give any suggestions.

> 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
>            Assignee: Grant Ingersoll
>            Priority: Minor
>             Fix For: 1.3
>
>         Attachments: SOLR-572.patch, SOLR-572.patch, SOLR-572.patch, 
> SOLR-572.patch, SOLR-572.patch, SOLR-572.patch, SOLR-572.patch, 
> SOLR-572.patch, SOLR-572.patch, SOLR-572.patch, SOLR-572.patch, 
> SOLR-572.patch, SOLR-572.patch, 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.

Reply via email to