lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Ganyo <scott.ga...@etapestry.com>
Subject Re: Adding lock timeouts to write.lock
Date Mon, 11 Aug 2003 20:08:33 GMT
Ok.  I'll buy that.  Consider the TIMEOUT constants moved.

Scott

Doug Cutting wrote:

> Scott Ganyo wrote:
>
>> Thanks, Doug.  Unfortunately, as you know, IndexWriter isn't the only 
>> one using these locks:
>>
>> 1) IndexReader uses the "commit.lock" when opening.
>>
>> 2) IndexReader needs to create a "write.lock" during the delete process.
>>
>> So, although perhaps not a perfect solution, it seems to me that Lock 
>> is still at least a common place to define these and less confusing 
>> than putting them on IndexWriter -- which is only one of the classes 
>> that use then contants.
>
>
> Yes, I realize that multiple classes use these constants.  But they're 
> only used in the index package, so I thought they'd be better off 
> there.  They're not used by anything in the storage package.  
> IndexWriter uses them the most, so it seems like the best place to me.
>
> Doug
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-dev-help@jakarta.apache.org


-- 
All progress is initiated by challenging current conceptions, and executed by supplanting
existing institutions. - George Bernard Shaw



Mime
View raw message