Dan, Thanks... I wasn't clear in the original email what the issue is. It's the fact that multiple terms are in the query, then no results are returned.
Thanks On Fri, Sep 3, 2010 at 8:33 AM, dan sutton <danbsut...@gmail.com> wrote: > I set this up a few years ago with something like the following: > > <fieldType name="autocomplete" class="solr.TextField"> > <analyzer type="index"> > <tokenizer class="solr.KeywordTokenizerFactory"/> > <filter class="solr.LowerCaseFilterFactory" /> > <filter class="solr.PatternReplaceFilterFactory" > pattern="([^a-z0-9])" replacement="" replace="all" /> > <filter class="solr.EdgeNGramFilterFactory" > maxGramSize="20" minGramSize="1" /> > </analyzer> > <analyzer type="query"> > <tokenizer class="solr.KeywordTokenizerFactory"/> > <filter class="solr.LowerCaseFilterFactory" /> > <filter class="solr.PatternReplaceFilterFactory" > pattern="([^a-z0-9])" replacement="" replace="all" /> > </analyzer> > </fieldType> > > <filter class="solr.PatternReplaceFilterFactory" pattern="([^a-z0-9])" > replacement="" replace="all" /> is the bit missing i think here > > This way the search is agnostic to case and any non-alphanum chars, this was > to facilitate a location autocomplete for searching > > So is was a basic search, returning the top N results along with additional > info to show in the autocomplete to our mod_perl servers, Results were > cached in the mod_perl servers. > > Regards, > Dan > > On Thu, Sep 2, 2010 at 1:53 PM, Jason Rutherglen <jason.rutherg...@gmail.com >> wrote: > >> I'm having a different issue with the EdgeNGram technique described >> here: >> http://www.lucidimagination.com/blog/2009/09/08/auto-suggest-from-popular-queries-using-edgengrams/ >> >> That is one word queries q=app on the query_text field, work fine >> however "q=app mou" do not. Why would this be or is there a >> configuration that could be missing? >> >> On Wed, Sep 1, 2010 at 3:53 PM, Eric Grobler <impalah...@googlemail.com> >> wrote: >> > 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 <rober...@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:impalah...@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 <rober...@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:jazzgl...@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 >> >> > >> >> > >> >> > >> >> >> > >> >
