Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of michael.wechner@wyona.com
 designates 195.226.6.75 as permitted sender)
Message-ID: <4EE79B27.1010507@wyona.com>
Date: Tue, 13 Dec 2011 19:36:23 +0100
From: Michael Wechner <michael.wechner@wyona.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: java-user@lucene.apache.org
Subject: How to use setWriteLockTimeout(long) when write.lock already exists
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Hi

According to

http://www.gossamer-threads.com/lists/lucene/java-dev/37421

one cannot overwrite the default write lock timeout of 1000ms once a 
write.lock already exists (for example inside a multi-threaded 
web-application), because in order to use the method  
setWriteLockTimeout(long)  one would have to
first create an instance of IndexWriter, but because write.lock already 
exists the creation will throw a LockObtainFailedException and hence 
once does not get an instance.

In the link above "Mike" is mentioned that he will create a Jira issue, 
but it's not clear to me if it ever got created
and/or that somebody tried to improve this. Any idea?

Just as a suggestions, but I think it would be nice if one could create 
an IndexWriter instance without actually opening the index in the first 
place, but rather something like:

IndexWriter iWriter = new IndexWriter();
iWriter.setDirectory(...);
iWriter.setAnalyzer(....);
iWriter.setWriteLockTimeout(75);
iWriter.open(); // or iWriter.checkout();
// do something with the index....
iWriter.close();

WDYT?

Thanks

Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org