lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Miller <markrmil...@gmail.com>
Subject Re: Calling indexWriter.close() in web app
Date Thu, 12 Jul 2007 00:45:05 GMT
The lock file is only for Writers. The lock file ensures that even two 
writers from two JVM's will not step on each other. Readers do not care 
about what the writers are doing or whether there is a lock file...even 
more so with the new generational files i believe.

- Mark

vcampa wrote:
> Steinert, Fabian wrote:
>   
>> Hi,
>> you do not need to writer.close() the IndexWriter at all to make changes
>> visible.
>> When IndexWriter is constructed with autoCommit = true flag set,
>> calling writer.flush() will do.
>>
>>     
>
> Ok, but what about the write.lock? IndexWriter releases its write.lock only
> when closed, so i think problems may begin when i try to open IndexReader on
> a locked index. I'm still confused... help.
>
>   

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


Mime
View raw message