[
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
OK, here's another crack at it. I think I fixed the field issue Oleg was
seeing (but haven't fully tested that) and I have it up and running in the Solr
example. After indexing the example docs there, try something like:
{code}
http://localhost:8983/solr/spellCheckCompRH/?q=iPoo+text:sola&version=2.2&start=0&rows=10&indent=on&spellcheck=true&spellcheck.build=true
{code}
to build it and spell check the query.
I also have, what I think is a good compromise on spell checking the
CommonParams.Q and the Spellcheck.Q, namely, the latter just uses a whitespace
tokenizer to create the tokens.
I am also thinking of adding a "collate" functionality, which would take the
top suggestions and splice them back into the original string, as this seems
like somehting many apps would like to have.
> 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
> 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, 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.
