[
https://issues.apache.org/jira/browse/SOLR-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915454#action_12915454
]
Grant Ingersoll commented on SOLR-1316:
---------------------------------------
FWIW, much of the docs are the same as the SpellCheckComponent. In fact, I'm
planning on implementing a Related Search capability, and it occurs to me that
Related Search, Spelling and AutoSuggest are all just variants of the same
thing (given a Query, give me suggestions for pertinent things around that
query), so I'm going to refactor things a little bit to reflect that. There
shouldn't be any functionality change. The only thing I was contemplating
changing was in the config the <spellcheck> tag be renamed as <suggestion> (it
would still accept the old, too). Code-wise, the gist of what I have in mind
is that there will be a SuggestionComponent and SpellCheckComp will just be a
empty, deprecated shell on that. Maybe would take SolrSpellChecker and rename
that (or pull it up a level) as SolrSuggester. Everything should still work
fine, but the nomenclature is better, I think.
Given the above, I think the docs could then be reworked to show the various
"suggestion" paths one might take: auto, spelling, related, other and how they
can be implemented and reuse the same input params and output responses.
> 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: Andrzej Bialecki
> Priority: Minor
> Fix For: Next
>
> Attachments: SOLR-1316.patch, SOLR-1316.patch, SOLR-1316.patch,
> SOLR-1316.patch, SOLR-1316.patch, SOLR-1316.patch, SOLR-1316.patch,
> SOLR-1316.patch, SOLR-1316.patch, SOLR-1316.patch, SOLR-1316.patch,
> SOLR-1316_3x-2.patch, SOLR-1316_3x.patch, 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]