Hi, Two weeks back I did have the problem which I stated. But I am unable to reproduce the results currently. I tested and retested but couldnt repeat the same. Doug have U guys fixed the issue long back itself ? (The only thing I have done fresh is to download the latest lucene-1.2-rc1.zip file and re-installed lucene - since it came along with source code)
:-) Regards, Sunil Zanjad -----Original Message----- From: Doug Cutting [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 23, 2001 1:48 AM To: '[EMAIL PROTECTED]'; 'Scott Ganyo'; [EMAIL PROTECTED] Subject: RE: new Lucene release: 1.2 RC2 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:[EMAIL PROTECTED]] > Sent: Monday, October 22, 2001 12:49 PM > To: Doug Cutting; 'Scott Ganyo'; [EMAIL PROTECTED] > Subject: RE: new Lucene release: 1.2 RC2 > > > > From: Sunil Zanjad [mailto:[EMAIL PROTECTED]] > > > > >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 >
