[EMAIL PROTECTED] writes:
> Hi Christoph,
>
> Thats what I thought. But what I'm seeing is this:
> - open
> reader for searching
> (the reader is opening an index on a remote machine
> (via UNC) which takes a couple seconds)
> - meanwhile the other service opens
> an IndexWriter and adds a docume
Daniel Taurat wrote:
Hi,
I have just another stupid parser question:
There seems to be a special handling of the dash sign "-" different from
Lucene 1.2 at least in Lucene 1.4.RC3
StandardAnalyzer.
From the behaviour you describe I think that the dash sign is removed
from the text by the analyz
I'm testing fault tollerance aspects of an application using Lucene.
Consider if power is pulled form the server/workstation and it
immediately shuts down hard or crashes.
I'm faced with a situation of a commit.lock file exising in the temp
directory. Lucene is throwing an exception when a write
I'm looking for tips on speeding up searches since I am a relatively new
user of Lucene.
I've created a single index with 4.5 million documents. The index has
about 22 fields and one of those fields is the contents of the body tag
which can range from 5K to 35K. When I create the field (named
The lucene-demo is now working fine outside the tomcat/webapps dir.
I created a folder, lets say 'c:/Test'. Copied the lucene-doxs to
that folder.
Afterwards I deployed the war file to this folder.
I created an index to 'c:/test/index' and modified the
configuratio
Hi,
I have just another stupid parser question:
There seems to be a special handling of the dash sign "-" different from
Lucene 1.2 at least in Lucene 1.4.RC3
StandardAnalyzer.
Examples (1.4RC3):
A document containing the string "dash-test" is matched by the following
search expressions:
dash
tes
