[
https://issues.apache.org/jira/browse/SOLR-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796182#action_12796182
]
Brad Giaccio commented on SOLR-1316:
------------------------------------
bq. We could do that but as Andrej noted, we'd end up re-implementing a lot of
its functionality. I'm not sure if it is worth it. I agree that it'd be odd
using parameters prefixed with "spellcheck" for auto-suggest and it'd have been
easier if it were vice-versa. Does anybody have a suggestion?
Couldn't you just extend the SpellCheckComponent, and make use of something
like COMPONENT_NAME or PARAM_PREFIX in the param calls instead of the static
string in SpellingParams? That way the autosuggestcomponent would have
COMPONENT_NAME=autoSuggest and the spelling would have it set to spelling then
let all the common code just live in the base class.
Just a thought
> Create autosuggest component
> ----------------------------
>
> Key: SOLR-1316
> URL: https://issues.apache.org/jira/browse/SOLR-1316
> Project: Solr
> Issue Type: New Feature
> Components: search
> Affects Versions: 1.4
> Reporter: Jason Rutherglen
> Assignee: Shalin Shekhar Mangar
> Priority: Minor
> Fix For: 1.5
>
> Attachments: suggest.patch, suggest.patch, suggest.patch, TST.zip
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Autosuggest is a common search function that can be integrated
> into Solr as a SearchComponent. Our first implementation will
> use the TernaryTree found in Lucene contrib.
> * Enable creation of the dictionary from the index or via Solr's
> RPC mechanism
> * What types of parameters and settings are desirable?
> * Hopefully in the future we can include user click through
> rates to boost those terms/phrases higher
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
