Can you post the full stack trace in both cases?
Mike
Chaula Ganatra wrote:
I found one case when such multiple files are remained, when we call
writer.optimise() it throws exception and multiple files remained in
index dir.
After such multiple files, when we add document in index by calling
writer.addDocument it throws java.lang.NegativeArraySizeException
Regards,
Chaula
-----Original Message-----
From: Grant Ingersoll [mailto:[EMAIL PROTECTED]
Sent: 26 September, 2008 6:02 PM
To: java-user@lucene.apache.org
Subject: Re: How to restore corrupted index
There is the CheckIndex tool included in the distribution for
checking/
fixing bad indexes, but it can't solve everything.
The bigger question is why it is happening to begin with. Can you
describe your indexing process? How do you know the index is actually
corrupted? Are you seeing exceptions when opening it?
-Grant
On Sep 26, 2008, at 6:49 AM, Chaula Ganatra wrote:
We have an application in which index will be updated frequently.
During development time, found that index files gets corrupted, i.e.
more than one cfs files,some other extension files e.g. frq, fnm,
nrm
Remains there in index directory.
Is there any way that such issue does not occur at all or if it
happens
we can recover the index data again?
It would be a great help, if some one can.
Regards,
Chaula
--------------------------
Grant Ingersoll
http://www.lucidimagination.com
Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
