RE: problems with last patch (obtain write.lock while deleting d ocuments)

[Doug Cutting <DC...@grandcentral.com>]

> From: Daniel Calvo [mailto:dcalvo@ig.com.br]
> 
> I've just updated my version (via CVS) and now I'm having 
> problems with document deletion. I'm trying to delete a document using
> IndexReader's delete(Term) method and I'm getting an IOException:
> 
> java.io.IOException: Index locked for write: 

Oops.  I think I see the problem.  I only tested this on an optimized index!

I just checked in a fix.  Try it and tell me how it goes.

Sorry for the inconvenience,

Doug

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: problems with last patch (obtain write.lock while deleting documents)

[Daniel Calvo <dc...@ig.com.br>]

Hi Doug,

Problem solved, thanks!

BTW, is the way I'm doing the deletion the correct one? I reckon I can't use a cached reader, since I have to close it after the
deletion to release the write lock. Does it make sense? Regarding writers, is it ok to share a single IndexWriter with multiple
writers, i.e., I have one writer adding a document and then I get another request for doc upload. I can't open a new IndexWriter
because of the write lock, so I'm using the one already available. After all writers are done, the IndexWriter is closed.

Again, thanks a lot (for the fix and, most important, for Lucene)

--Daniel

> -----Original Message-----
> From: Doug Cutting [mailto:DCutting@grandcentral.com]
> Sent: domingo, 10 de fevereiro de 2002 19:55
> To: 'Lucene Users List'
> Subject: RE: problems with last patch (obtain write.lock while deleting
> documents)
>
>
> > From: Daniel Calvo [mailto:dcalvo@ig.com.br]
> >
> > I've just updated my version (via CVS) and now I'm having
> > problems with document deletion. I'm trying to delete a document using
> > IndexReader's delete(Term) method and I'm getting an IOException:
> >
> > java.io.IOException: Index locked for write:
>
> Oops.  I think I see the problem.  I only tested this on an optimized index!
>
> I just checked in a fix.  Try it and tell me how it goes.
>
> Sorry for the inconvenience,
>
> Doug
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>