[jira] Commented: (SOLR-572) Spell Checker as a Search Component

[Grant Ingersoll (JIRA)]

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

Grant Ingersoll commented on SOLR-572:
--------------------------------------

Also included in that last patch is a (proposed) sample configuration:

{code}
<searchComponent name="spellcheck" 
class="org.apache.solr.handler.component.SpellCheckComponent">
    <lst name="spellchecker">
      <str 
name="classname">org.apache.solr.spelling.IndexBasedSpellChecker</str>
        <lst name="dictionary">
          <str name="name">default</str>
          <str name="field">word</str>
          <str name="indexDir">c:/temp/spellindex</str>
        </lst>
    </lst>
    <lst name="spellchecker">
      <str name="classname">org.apache.solr.spelling.FileBasedSpellChecker</str>
      <lst name="dictionary">
        <str name="name">external</str>
        <str name="sourceLocation">spellings.txt</str>
        <str name="characterEncoding">UTF-8</str>
        <str name="spellcheckIndexDir ">./spellchecker</str>
      </lst>

    </lst>


  </searchComponent>
{code}

> 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
>             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
>
>
> 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.