lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bojan Smid (JIRA)" <>
Subject [jira] Commented: (SOLR-572) Spell Checker as a Search Component
Date Fri, 16 May 2008 13:11:55 GMT


Bojan Smid commented on SOLR-572:

The "field" attribute for file-based dictionary is basically the same "field" attribute as
in default dictionary (in both cases they are used to obtain query analyzer), so that is the
reason why I used the same name. My question was is it ok for default dictionary to use the
same field to build dictionary from solr index and to obtain query analyzer for extracting

> Spell Checker as a Search Component
> -----------------------------------
>                 Key: SOLR-572
>                 URL:
>             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
> 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.

View raw message