Return-Path: X-Original-To: apmail-lucene-java-user-archive@www.apache.org Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D9E4E5C4 for ; Fri, 6 May 2011 09:12:42 +0000 (UTC) Received: (qmail 56207 invoked by uid 500); 6 May 2011 09:12:40 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 56171 invoked by uid 500); 6 May 2011 09:12:40 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 56163 invoked by uid 99); 6 May 2011 09:12:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 May 2011 09:12:40 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dawid.weiss@gmail.com designates 209.85.161.48 as permitted sender) Received: from [209.85.161.48] (HELO mail-fx0-f48.google.com) (209.85.161.48) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 May 2011 09:12:34 +0000 Received: by fxm7 with SMTP id 7so3803316fxm.35 for ; Fri, 06 May 2011 02:12:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=rMN94j9yzN5WN7lwbCU8Cp+jNAPRFzwnyzUoc3FTeRE=; b=OfWUk5cBkueArulEfrzImJAi4j6DFpCHR7PWsSeFku2zQyLWYG5aKsCQLrXt4vozoY bDoB261s2a+QwuKKugwhmQG+m2iLaoNQoJoyNWLHczZyZBWTAk0rJcLCpts1U1T05N1C daKHvuy8zzMi3Umu5M+qyuiUIjkRVoiOAEydQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=i1yCsOo+0g6zVPQM1v0rf829pVHNB9j5UbCznBgoK3D1iTzG9foxz6QgqVtPFuwuAM afjB9zvrxkvC6Mavlt2PHD1g+wFN8kzqXJmhaoYbOZX9yv/Y+70bq07in/NzcgWCofnG IUa9/obg8MibTLaRPbiFvivhV/9Lakiw+WEns= Received: by 10.223.24.153 with SMTP id v25mr159300fab.29.1304673133901; Fri, 06 May 2011 02:12:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.5.91 with HTTP; Fri, 6 May 2011 02:11:34 -0700 (PDT) In-Reply-To: References: From: Dawid Weiss Date: Fri, 6 May 2011 11:11:34 +0200 Message-ID: Subject: Re: Using Solr's (Auto)suggest with plain lucene To: java-user@lucene.apache.org Content-Type: multipart/alternative; boundary=00151747342cb2a16a04a297e265 X-Virus-Checked: Checked by ClamAV on apache.org --00151747342cb2a16a04a297e265 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 1. FSTLookup is in the trunk only, it has not been released. 2. Case-insensitive lookups are possible, you'd just need to pass normalize= d tokens from which the dictionary is built and then use the same normalization at the time you query for suggestions. 3. "http://search-lucene.com/m/586gA4ccL11". I have no idea. Dawid On Fri, May 6, 2011 at 11:06 AM, Clemens Wyss wrote: > I have come across TSTLookup. > In which jar Do I find FSTLookup? Does any of these lookup-classes allow > case insensitive lookups? My terms are (unfortunately) cased. > > What Lookup "sits" behind this suggester > http://search-lucene.com/m/586gA4ccL11 > here? > > > > -----Urspr=C3=BCngliche Nachricht----- > > Von: Dawid Weiss [mailto:dawid.weiss@gmail.com] > > Gesendet: Donnerstag, 5. Mai 2011 15:00 > > An: java-user@lucene.apache.org > > Betreff: Re: Using Solr's (Auto)suggest with plain lucene > > > > If you check out the source code of solr/lucene, look at FSTLookup clas= s > and > > FSTLookupTest -- you can populate FSTLookup manually with terms/ phrase= s > > from your index and then use the resulting automaton for suggestions. > > > > Dawid > > > > On Thu, May 5, 2011 at 2:54 PM, Clemens Wyss > > wrote: > > > > > I have implemented my index (in fact it's a plugable indexing API) in > > > "plain Lucene". It tried to implement a term suggestion mechanism on > > > my own, being not to happy so far. > > > At > > > http://search- > > lucene.com/m/0QBv41ssGlh/suggestion&subj=3DAuto+Suggest > > > I have seen Solr's auto suggestion for search terms. Appart from not > > > being "fuzzy" it looks quite promising. > > > > > > How easily can I Integrate Solr's suggestion with my Lucene index? > > > > > > Thx > > > Clemens > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org > > > For additional commands, e-mail: java-user-help@lucene.apache.org > > > > > > > --00151747342cb2a16a04a297e265--