On May 27, 2008, at 8:25 PM, Oleg Gnatovskiy (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SOLR-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600323
#action_12600323 ]
Oleg Gnatovskiy commented on SOLR-572:
--------------------------------------
I am still confused about my NPE. Was that a config issue on my
part, or was it a bug? The way Grant said he was working on it, I
assumed that it was a bug :-)
Sorry, I meant I was working on the token alignment issue. I will
look at this, too, though.
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
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.
