[
https://issues.apache.org/jira/browse/SOLR-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599202#action_12599202
]
Shalin Shekhar Mangar commented on SOLR-572:
--------------------------------------------
Otis -- Sorry, I missed your post earlier. I can't think of a use-case for
adding frequency information to plain text files. Spell checker's utility comes
from the fact that it can suggest keywords for which Solr can return documents.
That is possible only when the tokens (or synonyms) are present in the Solr
index. Plain text dictionaries will be used to add additional common keywords
which may not be in the Solr fields used for suggestions but may be present in
huge fields which you don't want to add to spell checker. For example, I may
build my index only on vehicle brands but I may like to include terms such as
"cars", "manufacturer", "make" from plain text files, which may be present in
my huge default search field. Since the intent would be just to match some
document with the given suggestion, frequency may not play a significant role
here, IMHO. What do you think?
Bojan -- I think we should include an "exists" flag in the response. As for
your point of queries with non-simple tokens, we can introduce another param
like "spellcheck.q" to which the application can set the simple query. End
users almost never know that Solr is running behind the scenes and the Solr
queries are constructed by the application itself which can send the simple
query in this way.
> 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
>
>
> 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.
