[
https://issues.apache.org/jira/browse/SOLR-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757688#action_12757688
]
Ankul Garg commented on SOLR-1316:
----------------------------------
For the purpose of benchmarking alone, I employed DFS just to find the
number of hits for each autocomplete. But to retrieve complete keys, just
create a string key variable in the TST node. In the insert function, where
end boolean has been declared to be true (the termination condition), key
can be assigned the complete string. I will modify the code and post it
soon. May be you can also do the changes as described above.
On Sun, Sep 20, 2009 at 12:11 AM, Andrzej Bialecki (JIRA)
> 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
> Priority: Minor
> Fix For: 1.5
>
> Attachments: suggest.patch, TernarySearchTree.tar.gz
>
> 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.
