[
https://issues.apache.org/jira/browse/SOLR-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bojan Smid updated SOLR-572:
----------------------------
Attachment: SOLR-572.patch
I added support for file-based dictionaries (they are configured as described
in Shalin's post) using Lucene's PlainTextDictionary.
However, I had to add property "field" to the configuration for this dictionary
in order to obtain analyzer (which is passed to FieldSpellChecker). This
analyzer is later used to extract tokens from the query.
I guess my current solution is not quite correct (since PlainTextDictionary
doesn't really need analyzer), but it also makes me wonder if in case of
dictionary built from solr index, same analyzer should be used when building
dictionary and parsing query strings?
> 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
> Fix For: 1.3
>
> Attachments: 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.
