lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Cutting <DCutt...@grandcentral.com>
Subject RE: new Lucene release: 1.2 RC2
Date Mon, 22 Oct 2001 20:18:22 GMT
If you think there is a bug, can you please provide a simple,
self-contained, reproducible test case that illustrates the problem.  You
could use Runtime.getRuntime().halt() to abruptly exit the JVM.

Thanks,

Doug


> -----Original Message-----
> From: Sunil Zanjad [mailto:sunilz@bsil.com]
> Sent: Monday, October 22, 2001 12:49 PM
> To: Doug Cutting; 'Scott Ganyo'; lucene-user@jakarta.apache.org
> Subject: RE: new Lucene release: 1.2 RC2
> 
> 
> > From: Sunil Zanjad [mailto:sunilz@bsil.com]
> >
> >   >Indexes left in an inconsistent state on crash (i don't
> >   > remember who
> >
> >   I believe that even I have reported it. This happens on
> > abrupt exit of the JVM
> >   To do this I had one thread updating a directory containing
> > many .txt files and
> >   I simply exited the program. Later when I ran the search,
> > it didnt give me the desired output.
> 
> >>That's actually the correct behavior.  If indexing is not 
> completed, with
> a
> >>call to IndexWriter.close(), then the index should appear unchanged.
> 
> >>Doug
> 
> But what happens to those files which I have indexed 
> successfully earlier?
> The search wouldnt retrieve results of the previous indexed files.
> Is this state correct?
> Please do clarify on this.
> 
> Regards,
> 
> Sunil Zanjad
> 

Mime
View raw message