lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Miller <markrmil...@gmail.com>
Subject Re: ReadOnly IndexReaders
Date Sat, 30 May 2009 17:27:00 GMT
Is there a valid use case? It seems like it might be a tricky method, 
because its an IndexReader property and not the index. A user should 
probably technically treat read-only/non-read-only the same because it 
does not imply a different IndexReader didn't make changes/do deletes?

It doesn't sync deletes, but should you use the API any differently?

I don't see it hurting anything of course, but is there a real use case?

 Grant Ingersoll wrote:
> OK, I'll do it.
>
> On May 30, 2009, at 8:29 AM, Michael McCandless wrote:
>
>> Makes sense!
>>
>> Mike
>>
>> On Fri, May 29, 2009 at 5:21 PM, Grant Ingersoll 
>> <gsingers@apache.org> wrote:
>>> Does it make sense to add isReadOnly() to IndexReader such that one can
>>> easily introspect whether a Reader is read only?
>>>
>>> -Grant
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: java-dev-help@lucene.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: java-dev-help@lucene.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>


-- 
- Mark

http://www.lucidimagination.com




---------------------------------------------------------------------
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