lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maik Schreiber <>
Subject Re: DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor
Date Sun, 22 May 2005 15:22:29 GMT
> I didn't follow this closely, but are you saying that
> LuceneIndexAccessor then replaces IOError caused by locking with
> blocking calls?  It sounds like the client of LuceneIndexAccessor still
> needs to keep track of open IndexReaders, IndexWriters, etc., or else
> one can end up with a hard-to-track blocked call somewhere in the code,
> no?  It would be nice to see how this works via a unit test.

Please see

The client just does getWriter(), getReader() or whatever it wishes, then
uses release() to give the instances back. The index accessor is responsible
for synchronizing access such that no two writers can be open at the same
time etc.

Maik Schreiber   *

GPG public key:
Key fingerprint: CF19 AFCE 6E3D 5443 9599 18B5 5640 1F11 D713

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message