Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 84130 invoked from network); 7 Oct 2008 18:00:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Oct 2008 18:00:21 -0000 Received: (qmail 24468 invoked by uid 500); 7 Oct 2008 18:00:13 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 24441 invoked by uid 500); 7 Oct 2008 18:00:13 -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 24423 invoked by uid 99); 7 Oct 2008 18:00:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Oct 2008 11:00:12 -0700 X-ASF-Spam-Status: No, hits=2.7 required=10.0 tests=DNS_FROM_OPENWHOIS,DNS_FROM_SECURITYSAGE,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Oct 2008 17:59:09 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KnGqW-0005dV-BN for java-user@lucene.apache.org; Tue, 07 Oct 2008 10:59:44 -0700 Message-ID: <19863821.post@talk.nabble.com> Date: Tue, 7 Oct 2008 10:59:44 -0700 (PDT) From: John G To: java-user@lucene.apache.org Subject: Re: Re-tokenized fields disappear In-Reply-To: <7E1E602E5D534D51882AB6FF738B57FC@desktop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: griffij@sosstaffing.com References: <7E1E602E5D534D51882AB6FF738B57FC@desktop> X-Virus-Checked: Checked by ClamAV on apache.org Thanks Erick, Yes PerFieldAnalyzerWrapper is my friend :>). Another related question, I'm putting these values into a document in fields with the same name. 'codesearch' e.g. "codesearch", "B05 1" "codesearch", "Q070301 4" etc. I read where only the last field entered is actually indexed but I can't find that post now. Is this true? How can I get around it? Thanks again. John G. John Griffin-3 wrote: > > My previous question may be moot but as is it is still a problem. Here's a > little more info on my problem. The same named fields contain two pieces > of > information, a code "B05" and a value "1" as follows. The value can be a > range such as 1 to 5 or 1 to 100. > > > > "codesearch", "B05 1" > > > > This field and other identically names but differently valued fields in > the > same document are related to a specific person as identified by another > field say SSN. So, one person can have multiple code searches. Both of the > codesearch values are related to one another and must be searchable such > as > > > > Return all persons with a codesearch value of B05 ranging from 1 to 3. > > > > How can I go about this? Do these codesearch fields need to be in a > separate > index related by SSN? > > > > Thanks in advance. > > > > John G. > > > -- View this message in context: http://www.nabble.com/Re-tokenized-fields-disappear-tp19850534p19863821.html Sent from the Lucene - Java Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org