lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ishan Chattopadhyaya <ichattopadhy...@gmail.com>
Subject Re: [jira] Commented: (SOLR-1316) Create autosuggest component
Date Thu, 17 Sep 2009 13:50:47 GMT
Andrzej, I think a splay tree will adjust itself to prioritize frequent user
queries. What do you think?

On Wed, Sep 16, 2009 at 11:45 PM, Andrzej Bialecki (JIRA)
<jira@apache.org>wrote:

>
>    [
> https://issues.apache.org/jira/browse/SOLR-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756149#action_12756149]
>
> Andrzej Bialecki  commented on SOLR-1316:
> -----------------------------------------
>
> bq. Andrej, why would immutability be a problem? Wouldn't we have to
> re-build the TST if the source index changes?
>
> Well, the use case I have in mind is a TST that improves itself over time
> based on the observed query log. I.e. you would bootstrap a TST from the
> index (and here indeed you can do this on every searcher refresh), but it's
> often claimed that real query logs provide a far better source of
> autocomplete than the index terms. My idea was to start with what you have -
> in the absence of query logs - and then improve upon it by adding successful
> queries (and removing least-used terms to keep the tree at a more or less
> constant size).
>
> Alternatively we could provide an option to bootstrap it from a real query
> log data.
>
> This use case requires mutability, hence my negative opinion about DAGWs
> (besides, we are lacking an implementation, don't we, whereas we already
> have a few suitable TST implementations). Perhaps this doesn't have to be an
> either/or, if we come up with a pluggable interface for this type of
> component?
>
> bq. I think the building of the data structure can be done in a way similar
> to what SpellCheckComponent does. [..]
>
> +1
>
>
> > 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.
>
>


-- 
---------------------------------------------------------------
Ishan Chattopadhyaya
Email: ishan@chattopadhyaya.com
Website: www.ishan.chattopadhyaya.com
---------------------------------------------------------------

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message