lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetic <otis_gospodne...@yahoo.com>
Subject Re: DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor
Date Sun, 22 May 2005 14:20:49 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.

Thanks for the contribution!

Otis


> http://issues.apache.org/bugzilla/show_bug.cgi?id=34995
> 
> ------- Additional Comments From
> blizzy-keyword-apache_bugs.e23ed5@blizzy.de  2005-05-22 14:52 -------
> So having said that, the component's purpose can be summarized as
> enforcing the
> IndexReader/IndexWriter/Searcher/Directory usage matrix (you cannot
> delete while
> adding documents etc.)


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


Mime
View raw message