lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Ingersoll (JIRA)" <>
Subject [jira] Commented: (SOLR-572) Spell Checker as a Search Component
Date Mon, 26 May 2008 15:15:56 GMT


Grant Ingersoll commented on SOLR-572:

If this is a default component, how do you setup the field to be used for spelling?  Are you
just using the default search field?  
Also, I don't think we should make it default, since there is this minor nit that it requires
building the index first.  I suppose that could be done on the first time spellings are requested,
but that seems like it could all of a sudden cause a much longer return.  By making it non-default,
I think it forces the person doing the configuration to think more about the setup, since
the setup of proper spelling is not trivial.

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