Maybe you should write your own analyzer for this case that changes all letters
to lower case but keeps all the numbers and signs as they are.
The other solution is not to use an analyzer for this field.
Frank
-Original Message-
From: M å n i s h [mailto:[EMAIL PROTECTED]
Sent:
, then may be it will
work.
-Original Message-
From: Kunemann Frank [mailto:[EMAIL PROTECTED]
Sent: Monday, September 26, 2005 12:28 PM
To: java-user@lucene.apache.org
Subject: RE: Problems in standard Analyzer
Maybe you should write your own analyzer for this case that changes all
What stops you from using the reader before you add the document to the
index?
Frank
-Original Message-
From: Beady Geraghty [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 15, 2005 2:30 AM
To: java-user@lucene.apache.org
Subject: input reader closed after
This depends on the analyzer you are using. You can find the standard
analyzers in org.apache.lucene.analysis. To find out what they do, I
recommend the example in Lucene in action in 4.2.3 called
AnalyzerDemo. If you don't have the book, you can also download the
examples from
Is there a good way to cancel a search? I mean e.g. after 10 seconds or if the
user changed his mind and wants to start another query.
Till now I didn't have a query that took longer than 10 secs, but this can
happen easily when the network connection is very slow or something like that.
I
The problem is that when searching there is no real save point to stop
the thread. The only line that takes time is this one:
Hits hits = searcher.search(query);
Frank
I've had such a long lasting search too. I sounds good to start the
search in another thread. I've done this for the indexing
a flag on each hit, and
throw an exception if it was set.
In a separate thread, you could set the flag to cancel the search.
-Yonik
Now hiring -- http://tinyurl.com/7m67g
On 9/8/05, Kunemann Frank [EMAIL PROTECTED] wrote:
The problem is that when searching there is no real save point to stop
