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

Otis Gospodnetic commented on SOLR-572:
---------------------------------------

I had a quick look and it all looks nice and clean.
I like the config, though I think "solr" is too specific - the source field 
could be in a vanilla Lucene indexthat lives somewhere on disk, or example.  
Thus, I'd change "solr" to "index".  Oh, I see, you are reading field values 
from the index of the current core.  I think that is fine, but wouldn't it also 
be good to be able to read field values from a vanilla Lucene index? (but you 
wouldn't know the field type and thus would not be able to get the Analyzer for 
the field)

Also, and regardless of the above, instead of having "indexDir" and "path", why 
not call them both "location" and maybe even let them include the file: schema 
for consistency, if it works with the code that uses those locations?

Also on TODO:
* Read dictionary from plain-text files.

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