lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Bialecki (JIRA)" <>
Subject [jira] Commented: (SOLR-1316) Create autosuggest component
Date Mon, 15 Feb 2010 12:31:28 GMT


Andrzej Bialecki  commented on SOLR-1316:

I would lean towards the latter - complex do-it-all components often suffer from creeping
featuritis and insufficient testing/maintenance, because there are few users that use all
their features, and few developers that understand how they work. I subscribe to the Unix
philosophy - do one thing, and do it right, so I think that if we can implement autosuggest
that works well from the technical POV, then it will become a reliable component that you
can combine in many creative ways to satisfy different scenarios, of which there are likely
many more than what you described ...

> 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, 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