Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
From: "Allen Atamer" <aatamer@casebank.com>
To: <lucene-user@jakarta.apache.org>
Subject: literal search in quotes on non-tokenized field
Date: Tue, 30 Nov 2004 16:42:44 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0642_01C4D6FB.9DF2B1C0"
Thread-Index: AcTXJYUuMotJ/kZGSOmA8Mcdpe/boA==
Message-ID: <TANGO0oaBfvQeVe0F7H00004a20@tango.casebank.com>

------=_NextPart_000_0642_01C4D6FB.9DF2B1C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Here is a problem I am experiencing with Lucene searches on non-tokenized
fields:
 
A search in quotes on a field named Build with the query "\"orig\"" does not
work but the query "origi" yields 62 hits
 
I have run indexing on the field with the following method
 
                    doc.add(Field.Keyword(data.getColumnName(j),
                            fieldValue.toString().toLowerCase()));
 
so even though the original data has "ORIGI" in the "Build" field, lowercase
is not the problem
 
Here's a log of the parsed query before going to the searcher:
 
Parsed query: (Build:"origi") for the first search
Parsed query: (Build:origi) for the second search
 
Right now we're not using a query parser / analyzer system to build the
query. We're building the query up.
The query mentioned above is a TermQuery object
 
Thanks 

------=_NextPart_000_0642_01C4D6FB.9DF2B1C0--