Return-Path: Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: (qmail 11849 invoked from network); 1 Sep 2010 19:35:14 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Sep 2010 19:35:14 -0000 Received: (qmail 4384 invoked by uid 500); 1 Sep 2010 19:35:12 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 4318 invoked by uid 500); 1 Sep 2010 19:35:11 -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 4310 invoked by uid 99); 1 Sep 2010 19:35:11 -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 19:35:11 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of impalaherd@googlemail.com designates 209.85.212.48 as permitted sender) Received: from [209.85.212.48] (HELO mail-vw0-f48.google.com) (209.85.212.48) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Sep 2010 19:35:07 +0000 Received: by vws4 with SMTP id 4so8988435vws.35 for ; Wed, 01 Sep 2010 12:34:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=ro+08zEQsymI4aTRwyku38U6Mp+motVGg0UZtYY8v30=; b=IONqoSjD++31DxuVhUVmLExUPWftIkbqFbNsuAnGrveSUg0KdpGF8ZNDyRgWeCUrL5 ui65hO/Ovb2fT5DVYw9bl1+dBMsI7T3Aar+mKT8V94Epoh6e6NeZESNe5804293G2M77 uY3kvOII8ttvPFg0Cp3HLNA0H3W9tT+iuvBfI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ZTmmhhJoZcWDjI8U/wt4xuEVcuFOzN+9D9MUDCRl0R7+FWz+BUaerXCC1xht+y7QWN CjOZol3L3w6BRjc08ahqBaQeE0S7m/n81yKbKd08WW8p7RJLlKgkSu6fmOnaYAdxa/9q AgqWz+0LO2G6/mmw41o+LwXOh7s2McvtLQKs8= MIME-Version: 1.0 Received: by 10.220.126.166 with SMTP id c38mr4608840vcs.52.1283369682532; Wed, 01 Sep 2010 12:34:42 -0700 (PDT) Received: by 10.220.180.138 with HTTP; Wed, 1 Sep 2010 12:34:42 -0700 (PDT) In-Reply-To: <11B8ADF3AAA0A84C89B1A42CADF918D305A557FA@email01> References: <11B8ADF3AAA0A84C89B1A42CADF918D305A557FA@email01> Date: Wed, 1 Sep 2010 20:34:42 +0100 Message-ID: Subject: Re: Auto Suggest From: Eric Grobler To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=0050450160f30afac3048f37ca9c --0050450160f30afac3048f37ca9c Content-Type: text/plain; charset=ISO-8859-1 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 > > > --0050450160f30afac3048f37ca9c--