OK, phew. Thanks for bringing closure here.
You mean you ran CheckIndex on the original index (input to scp) and
it was fine, but CheckIndex on the copy produced by scp showed the
corruption?
I think it's unusual for scp to corrupt the copy unless something
catastrophic happens (eg disk full, disk is bad, RAM is bad, etc.).
Mike
crspan wrote:
Thanks so much, Mike. Those runtime errors were caused by one
corrupted index, somehow corrupted during scp. It has Nothing to do
with lucene 2.3.2.
For those who come by this thread:
Please "CheckIndex"
That would saved me many hours of fruitless debugging.
Cheers,
Charlie
Michael McCandless wrote:
Hi,
Could you run org.apache.lucene.index.CheckIndex on your index and
post the result?
Are these exceptions easily reproduced starting from scratch (new
index)?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
