But it doesn't help the library. It can't assume there are no deletes just because the reader is read only. And if you know you don't do deletes you can skip calling isdeleted readonly or not. The only way this works cleanly is if you could ask if the "index" is readonly, not the Reader. Knowing a Reader is read-only does not help a generic Lucene library from calling isDeleted - it still must be called in a generic library - only the specific app would know it could be skipped, because it would know the "index" is read-only, not just the transient Reader.

On Mon, Jun 1, 2009 at 5:58 PM, Grant Ingersoll <gsingers@apache.org> wrote:

On Jun 1, 2009, at 8:48 AM, Mark Miller wrote:

Right. The app will know if the index is readonly.

Yes, but a library that was passed the reader may not.

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