From lucene-user-return-172-qmlist-jakarta-archive-lucene-user=jakarta.apache.org@jakarta.apache.org Wed Oct 31 17:20:20 2001 Return-Path: Delivered-To: apmail-jakarta-lucene-user-archive@apache.org Received: (qmail 54025 invoked from network); 31 Oct 2001 17:20:20 -0000 Received: from unknown (HELO osaka.betaversion.org) (192.18.49.133) by daedalus.apache.org with SMTP; 31 Oct 2001 17:20:20 -0000 Received: (qmail 21375 invoked from network); 31 Oct 2001 17:22:31 -0000 Received: from nagoya.betaversion.org (192.18.49.131) by osaka.betaversion.org with SMTP; 31 Oct 2001 17:22:31 -0000 Received: (qmail 5992 invoked by uid 97); 31 Oct 2001 17:20:21 -0000 Delivered-To: qmlist-jakarta-archive-lucene-user@jakarta.apache.org Received: (qmail 5940 invoked by uid 97); 31 Oct 2001 17:20:19 -0000 Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Users List" Reply-To: "Lucene Users List" Delivered-To: mailing list lucene-user@jakarta.apache.org Received: (qmail 5927 invoked from network); 31 Oct 2001 17:20:18 -0000 Message-ID: <4BC270C6AB8AD411AD0B00B0D0493DF0EE7CCE@mail.grandcentral.com> From: Doug Cutting To: 'Lucene Users List' Subject: RE: Querying an exact string match ? Date: Wed, 31 Oct 2001 09:08:59 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This should work. You should be able to find an un-tokenized field containing spaces with a TermQuery. Nothing should ever tokenize the string. Can you please supply a simple, self-contained example showing that this does not work? Thanks, Doug > -----Original Message----- > From: Winton Davies [mailto:wdavies@overture.com] > Sent: Wednesday, October 31, 2001 1:03 AM > To: lucene-user@jakarta.apache.org > Subject: Querying an exact string match ? > > > Hi, > > I have a field which I need to match exactly -- Ideally it > shouldn't > even be tokenized, but I can't find a way to do that -- adding a > field that is indexed but not tokenized, doesn't seem to work -- or > at least a Term Query doesn't work. > > eg the field is "x y z" -- and I do a phrase query "x y" it should > not match -- just "x y z" should match. > > Cheers, > Winton > > -- > To unsubscribe, e-mail: > > For additional commands, e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: