[
https://issues.apache.org/jira/browse/SOLR-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599166#action_12599166
]
Grant Ingersoll commented on SOLR-572:
--------------------------------------
OK, I'm working on this.
Some thoughts:
1. Why is the initialization done in prepare? Just to be a little more lazy
than in init?
2. In FieldSpellChecker, the getSuggestion method goes through and creates the
suggested map, but then the loop over the entry set at the end only uses the
value. I think our response should return the associated correction with the
original token.
3. I'm working on the abstraction notion. Basic idea is to pass off and create
something like AbstractSpellChecker with a LuceneSpellChecker instantiation and
handles the loading, etc. like is currently in the SpellCheckComponent and
implements getSuggestion() like you have. The goal is to have a common
response, no matter the spell checker, so that we can plug and play spell
checkers. I hope to have a patch soon.
> 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
>
>
> 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.
