lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Grobler <impalah...@googlemail.com>
Subject Re: Auto Suggest
Date Wed, 01 Sep 2010 20:53:52 GMT
Thanks for your feedback Robert,

I will try that and see how Solr performs on my data - I think I will create
a field that contains only important key/product terms from the text.

Regards
Johan

On Wed, Sep 1, 2010 at 9:12 PM, Robert Petersen <robertpe@buy.com> wrote:

> We don't have that many, just a hundred thousand, and solr response
> times (since the index's docs are small and not complex) are logged as
> typically 1 ms if not 0 ms.  It's funny but sometimes it is so fast no
> milliseconds have elapsed.  Incredible if you ask me...  :)
>
> Once you get SOLR to consider the whole phrase as just one big term, the
> wildcard is very fast.
>
> -----Original Message-----
> From: Eric Grobler [mailto:impalaherd@googlemail.com]
> Sent: Wednesday, September 01, 2010 12:35 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Auto Suggest
>
> Hi Robert,
>
> Interesting approach, how many documents do you have in Solr?
> I have about 2 million and I just wonder if it might be a bit slow.
>
> Regards
> Johan
>
> On Wed, Sep 1, 2010 at 7:38 PM, Robert Petersen <robertpe@buy.com>
> wrote:
>
> > I do this by replacing the spaces with a '%' in a separate search
> field
> > which is not parsed nor tokenized and then you can wildcard across the
> > whole phrase like you want and the spaces don't mess you up.  Just
> store
> > the original phrase with spaces in a separate field for returning to
> the
> > front end for display.
> >
> > -----Original Message-----
> > From: Jazz Globe [mailto:jazzglobe@hotmail.com]
> > Sent: Wednesday, September 01, 2010 7:33 AM
> > To: solr-user@lucene.apache.org
> > Subject: Auto Suggest
> >
> >
> > Hallo
> >
> > How would one implement a multiple term auto-suggest feature in Solr
> > that is filter sensitive?
> > For example, a user enters :
> > "mp3"
> >  and solr might suggest:
> >  ->   "mp3 player"
> >  ->   "mp3 nano"
> >  ->   "mp3 sony"
> > and then the user starts the second word :
> > "mp3 n"
> > and that narrows it down to:
> >  -> "mp3 nano"
> >
> > I had a quick look at the Terms Component.
> > I suppose it just returns term totals for the entire index and cannot
> be
> > used with a filter or query?
> >
> > Thanks
> > Johan
> >
> >
> >
>

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