Right. The app will know if the index is readonly. isReadonly would
only tell you the reader was readonly, not the index. A readonly
reader can be opened on an index with deletes. That why it's tricky.
It's not useful for what you might think you would use it for. At
least pure API wise.
- Mark
http://www.lucidimagination.com (mobile)
On Jun 1, 2009, at 8:40 AM, Yonik Seeley <yo...@lucidimagination.com>
wrote:
On May 30, 2009, at 13:27, Mark Miller <markrmil...@gmail.com> wrote:
Is there a valid use case? It seems like it might be a tricky
method,
because its an IndexReader property and not the index.
But it's just a flag passed in
If you know it's read only and that there are no deletes, can't you
avoid
isDeleted all together?
If you know there are no deletes, you should be able to avoid calling
isDeleted anyway.
-Yonik
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
