[
https://issues.apache.org/jira/browse/SOLR-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756094#action_12756094
]
Shalin Shekhar Mangar commented on SOLR-1316:
---------------------------------------------
bq. DAWGs are problematic, because they are essentially immutable once created
(the cost of insert / delete is very high)
Andrej, why would immutability be a problem? Wouldn't we have to re-build the
TST if the source index changes?
bq. Also, I think that populating TST from the index would have to be
discriminative, perhaps based on a threshold
I think the building of the data structure can be done in a way similar to what
SpellCheckComponent does. We can re-use the HighFrequencyDictionary which can
give tokens above a certain threshold frequency. The field names to use for
building the data structure and the analysis can also be done like SCC. The
response format for this component can also be similar to SCC.
> 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: 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.
