lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 11109] - Search lock file location should be configurable and favored over disableLuceneLocks property
Date Mon, 09 Sep 2002 14:43:48 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11109>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11109

Search lock file location should be configurable and favored over disableLuceneLocks property





------- Additional Comments From otis@apache.org  2002-09-09 14:43 -------
I just took a quick look at the Lucene's source.
It looks like commit.lock in IndexReader (used for searches) is made via
(FS)Directory's makeLock method, which makes use of the disableLuceneLocks, so I
think this will disable lock creation during searches.  Therefore, your searches
with a different user ID should work if the user has read permissions on the
index directory and files.
Could you please try it and post the results (i.e. error, if you get it)?
Thanks.

--
To unsubscribe, e-mail:   <mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:lucene-dev-help@jakarta.apache.org>


Mime
View raw message