Return-Path: Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: (qmail 23967 invoked from network); 1 Sep 2010 20:11:49 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Sep 2010 20:11:49 -0000 Received: (qmail 57829 invoked by uid 500); 1 Sep 2010 20:11:47 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 57719 invoked by uid 500); 1 Sep 2010 20:11:46 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 57709 invoked by uid 99); 1 Sep 2010 20:11:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Sep 2010 20:11:46 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of robertpe@buy.com designates 209.67.181.94 as permitted sender) Received: from [209.67.181.94] (HELO OutboundSMTP02.buycorp.buyservices.com) (209.67.181.94) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Sep 2010 20:11:41 +0000 Received: from email01.buy.com ([10.10.0.183]) by OutboundSMTP02.buycorp.buyservices.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 1 Sep 2010 13:11:21 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Auto Suggest Date: Wed, 1 Sep 2010 13:12:28 -0700 Message-ID: <11B8ADF3AAA0A84C89B1A42CADF918D305A557FB@email01> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Auto Suggest thread-index: ActKDMwO0R8ZCdNBR7iBBS7InxvfNQABGbDg References: <11B8ADF3AAA0A84C89B1A42CADF918D305A557FA@email01> From: "Robert Petersen" To: X-OriginalArrivalTime: 01 Sep 2010 20:11:21.0165 (UTC) FILETIME=[D828E7D0:01CB4A11] 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]=20 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 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 > > >