. Or just downcase the text
yourself first.
--
Ian.
On Tue, Feb 2, 2010 at 9:30 PM, java8964 java8964
java8...@hotmail.com wrote:
Is there an analyzer like keyword analyzer, but will also lowering
the data from lucene? Or I have to do a customer analyzer by myself
.
On Tue, Feb 2, 2010 at 8:56 PM, java8964 java8964 java8...@hotmail.com
wrote:
Hi, I have the following test case point to the index generated in our
application. The result is confusing me and I don't know the reason.
Lucene version: 2.9.0
JDK 1.6.0_18
public class IndexTest1
Hi, I have the following test case point to the index generated in our
application. The result is confusing me and I don't know the reason.
Lucene version: 2.9.0
JDK 1.6.0_18
public class IndexTest1 {
public static void main(String[] args) {
try {
FSDirectory directory
the wild card search, will lucene 2.9.0 to convert the
search string to lower case?
Date: Mon, 1 Feb 2010 20:36:29 +0200
Did you try queryParser.SetLowercaseExpandedTerms(false)?
DIGY
-Original Message-
From: java8964 java8964 [mailto:java8...@hotmail.com]
Sent: Monday
I noticed a strange result from the following test case. For wildcard search,
my understanding is that lucene will NOT use any analyzer on the query string.
But as the following simple code to show, it looks like that lucene will lower
case the search query in the wildcard search. Why? If not,
Message-
From: java8964 java8964 [mailto:java8...@hotmail.com]
Sent: Monday, February 01, 2010 5:27 PM
To: java-user@lucene.apache.org
Subject: During the wild card search, will lucene 2.9.0 to convert the
search string to lower case?
I noticed a strange result from
string to lower case?
Date: Mon, 1 Feb 2010 20:36:29 +0200
Did you try queryParser.SetLowercaseExpandedTerms(false)?
DIGY
-Original Message-
From: java8964 java8964 [mailto:java8...@hotmail.com]
Sent: Monday, February 01, 2010 8:11 PM
To: java-user@lucene.apache.org
Subject: RE
Hi,
In our application, we will allow the user to create a primary key defined in
the document. We are using lucene 2.9.
In this case, when we index the data coming from the client, if the metadata
contains the primary key defined,
we have to do the search/update for every row based on the
.
But this really *requires* that your PKs are single terms in a field. If
your PKs
are some sort of composite field, perhaps the iw.DeleteDocuments(Query[])
would help where each query is enough to uniquely identify your document.
Best
Erick
On Mon, Nov 16, 2009 at 12:15 PM, java8964 java8964
the Document you want to add. This is the
traditional way to do updates, and it is fast.
-jake
On Mon, Nov 16, 2009 at 9:15 AM, java8964 java8964
java8...@hotmail.comwrote:
Hi,
In our application, we will allow the user to create a primary key defined
in the document. We
Hi, I have a problem to work support the NumericField in query parser.
My environment is like this:
Windows XP with
C:\work\ java -version
java version 1.6.0_10
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)
I am using
11 matches
Mail list logo