[
https://issues.apache.org/jira/browse/SOLR-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-572:
---------------------------------
Attachment: SOLR-572.patch
WARNING: This patch compiles _ONLY_. I do NOT claim it is semantically
equivalent to the earlier patches although that is my goal and I don't think I
am far off. I have not tested it in any way, shape or form. I am only putting
it up here as a first cut of the abstractions I have in mind, so please provide
feedback based on that, especially in regards to the SolrSpellChecker class.
Most interesting, there, is the passing in of the IndexReader. I know not all
spellers are going to need the IndexReader, so ideally, it would be something
that is passed in or set during the construction of the speller, but I don't
think that will work, or at least I am not aware of how to make it work just
yet.
My next step is to add unit tests of the individual spell checkers and then the
component itself.
> 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, 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.
