[
https://issues.apache.org/jira/browse/SOLR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478900
]
Adam Hiatt commented on SOLR-81:
--------------------------------
In essence, point 1) is true. However, the way I have been using the
SpellChecker index allows for the user to have a standalone spell checker as
well as piggy-backing it off a primary index.
Point 2) prevents the second use case I mentioned and also limits what can be
done with the SpellChecker.
WRT the issue of the NGram/EdgeNGram tokenizers: These should probably be split
out into a separate patch/issue as they are not critical to the implementation.
I like the idea of providing the SpellChecker index access functionality as a
contrib that can be accessed from any RequestHandler, but it is useful to have
a separate RequestHandler that can just provide spell checking functionality
alone.
> Add Query Spellchecker functionality
> ------------------------------------
>
> Key: SOLR-81
> URL: https://issues.apache.org/jira/browse/SOLR-81
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Otis Gospodnetic
> Priority: Minor
> Attachments: SOLR-81-edgengram-ngram.patch,
> SOLR-81-ngram-schema.patch, SOLR-81-ngram.patch, SOLR-81-ngram.patch,
> SOLR-81-ngram.patch, SOLR-81-ngram.patch, SOLR-81-spellchecker.patch,
> SOLR-81-spellchecker.patch
>
>
> Use the simple approach of n-gramming outside of Solr and indexing n-gram
> documents. For example:
> <doc>
> <field name="word">lettuce</field>
> <field name="start3">let</field>
> <field name="gram3">let ett ttu tuc uce</field>
> <field name="end3">uce</field>
> <field name="start4">lett</field>
> <field name="gram4">lett ettu ttuc tuce</field>
> <field name="end4">tuce</field>
> </doc>
> See:
> http://www.mail-archive.com/[email protected]/msg01254.html
> Java clients: SOLR-20 (add delete commit optimize), SOLR-30 (search)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
