lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <>
Subject [jira] Commented: (SOLR-1316) Create autosuggest component
Date Thu, 10 Dec 2009 12:26:20 GMT


Shalin Shekhar Mangar commented on SOLR-1316:

I've started looking into the patch. 

# Why do we concatenate all the tokens into one before calling Lookup#lookup? It seems we
should be getting suggestions for each token just as SpellCheckComponent does.
# Related to #1, the Lookup#lookup method should return something more fine grained rather
than a SpellingResult
# Has anyone done any benchmarking to figure out the data structure we want to go ahead with?

I love that we are (ab)using the SpellCheckComponent. The good part is that if we go this
route, this auto-suggest pseudo-component will automatically work with distributed setups.

> Create autosuggest component
> ----------------------------
>                 Key: SOLR-1316
>                 URL:
>             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,
>   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.

View raw message