: Setting the COMMIT lock timeout.
On Dienstag 14 März 2006 10:52, Jim Bedford-roberts wrote:
Admittedly we could have developed a single central search component,
but given the way the code has evolved our current approach is simplest
for us. With separate application instances sharing access
while using singleton IndexSearchers in
each application.
-Original Message-
From: Daniel Naber [mailto:[EMAIL PROTECTED]
Sent: 13 March 2006 23:23
To: java-user@lucene.apache.org
Subject: Re: Setting the COMMIT lock timeout.
On Montag 13 März 2006 22:24, Bill Janssen wrote:
The default
I'm confused about how to set the COMMIT lock timeout since the version
1.9.1 release.
I note that this can't be set from system properties anymore
(CHANGES.txt, changes in run time behaviour 7), but am unable to find
the replacement setter method promised for IndexWriter.
Can anyone point
On Montag 13 März 2006 15:50, Jim Bedford-roberts wrote:
I note that this can't be set from system properties anymore
(CHANGES.txt, changes in run time behaviour 7), but am unable to find
the replacement setter method promised for IndexWriter.
Seems these have been forgotten. They can easily
Daniel Naber ponders:
Seems these have been forgotten. They can easily be added, but I still
wonder what the use case is to set these values?
The default value isn't magic. The appropriate value is
context-specific. I've got some people using Lucene on machines with
slow disks, and we need
