Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 51935 invoked from network); 1 Nov 2005 15:27:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Nov 2005 15:27:59 -0000 Received: (qmail 17043 invoked by uid 500); 1 Nov 2005 15:27:53 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 17022 invoked by uid 500); 1 Nov 2005 15:27:52 -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 17009 invoked by uid 99); 1 Nov 2005 15:27:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2005 07:27:52 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [128.230.18.29] (HELO mailer.syr.edu) (128.230.18.29) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2005 07:27:48 -0800 Received: from [128.230.38.212] (syru38-212.syr.edu) by mailer.syr.edu (LSMTP for Windows NT v1.1b) with SMTP id <0.14A19C8D@mailer.syr.edu>; Tue, 1 Nov 2005 10:27:30 -0500 Message-ID: <43678961.1050506@syr.edu> Date: Tue, 01 Nov 2005 10:27:29 -0500 From: Steven Rowe User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050411) X-Accept-Language: en-us, en MIME-Version: 1.0 To: java-user@lucene.apache.org Subject: Re: Search problems References: <1130853367.22840.72.camel@localhost.localdomain> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Such an analyzer already exists, in Lucene's Subversion repository, under contrib/analyzers/: KeywordAnalyzer. Robert Watkins wrote: > One approach for matching your queries with Luke would be to write a > custom Analyzer that does absolutely nothing to the terms. Then, if you > put this Analyzer in your classpath when running Luke you can select it > as the Analyzer you want Luke to use to tokenize your query. This is > not, of course, the approach you would want to take in your application, > but at least it will allow you to use Luke as you have specified. > > -- Robert Watkins > > On Tue, 1 Nov 2005, Miles Barr wrote: > >> On Thu, 2005-10-27 at 16:35 -0400, Sharma, Siddharth wrote: >> >>> My index has 4 keyword fields and one unindexed field. >>> I want to search by the 4 keyword fields and return the one unindexed >>> field. >>> >>> I can iterate over the documents via Luke. >>> But when I search for the same values that I see via Luke, it does >>> not find >>> the document. >>> >>> [ snipped ] >>> >>> What could the problem be? Any ideas? >>> I have added all the 4 fields with 'Field.Keyword'. >> >> >> Field.Keyword requires an exact match, i.e. you should manually create a >> TermQuery. Luke will analyze your query and hence tokenise it. Almost >> certainly the tokens it creates won't match the values in your field, >> because they have to be an exact match. >> >> [ snipped ] --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org