[
https://issues.apache.org/jira/browse/SOLR-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597358#action_12597358
]
Otis Gospodnetic commented on SOLR-572:
---------------------------------------
I see (indexDir comment). Might be better to make it more obvious then -
"sourceIndex" for the Lucene index that serves as the source of data) vs.
"targetIndex" (or "spellcheckerIndex") for the resulting spellchecker index.
For Lucene indices to be used as sources of data type="index",
field="fieldName", location="path/to/lucene/index/directory" makes sense.
Ignore my comment about the schema, I'm just complicating things with that.
Yes, one word per line for plain-text file data sources - that can easily be
digested with PlainTextDictionary class (part of Lucene SC).
> 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.
