The best suggestion I have is to look at the code in my first java.net
article (Intro Lucene) and borrow the Analyzer utility code to see what
happens to a sample string as it is analyzed. Then pass that same
string to QueryParser (along with the same analyzer) and see what the
Query.toString(
I'm having problems searching for an exact match with a phrase.
Essentially, I think my problem is that the tokenizer is tossing the
double quotes around the phrase, tokenizing each word and so I end up
with the document hit I want plus several more I don't (the latter
having some of the words, but
Suggestion: make sure the NFS lock daemon (lockd) is running on the NFS
server.
Peter
- Original Message -
From: "Dmitri Ilyin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 03, 2004 1:09 PM
Subject: weblogic cluster, index on NFS and locking problem
> Hi,
>
> We
Hi,
We run our application on weblogic cluster. the lucene index service
runs on both server in cluster and they both write to one index
directory, shared via NFS. We have experenced a problem with commit.lock
file, that seems not to be deleted and stayed in the index directory, so
we could no
On Feb 3, 2004, at 7:12 AM, Erik Hatcher wrote:
Doug asked me to take care of the logistics of pushing the Lucene 1.3
FINAL release to the Apache site properly so that it is mirrored
worldwide. Last weekend I said the right magic incantations and it
looks like it has been successful. So, witho
Doug asked me to take care of the logistics of pushing the Lucene 1.3
FINAL release to the Apache site properly so that it is mirrored
worldwide. Last weekend I said the right magic incantations and it
looks like it has been successful. So, without further ado, Lucene 1.3
is now completely of
