[
https://issues.apache.org/jira/browse/SOLR-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880751#action_12880751
]
Ankul Garg commented on SOLR-1316:
----------------------------------
Stefan, yes the tree needs to be re-built at each commit. But, I think the
problem can be overcome. This can be done by implementing the ternary tree to
be self-balancing. Thus, inserting and deleting strings won't affect the
balancing of the tree. But, does the commit operation gives us a new set of
tokens altogether, or can we have separate sets of newly added tokens and
deleted tokens? The latter can help the trick come into action.
> 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: Next
>
> Attachments: SOLR-1316.patch, SOLR-1316.patch, SOLR-1316.patch,
> SOLR-1316.patch, SOLR-1316.patch, SOLR-1316.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]
