[prev in list] [next in list] [prev in thread] [next in thread]
List: lucene-user
Subject: Re: Corrupted index
From: Bill Tschumy <bill () otherwise ! com>
Date: 2005-04-11 13:29:16
Message-ID: ed783268cc76fb983e5c4fd6799b1625 () otherwise ! com
[Download RAW message or body]
Daniel,
Thanks for responding on this thread. I doubt the copy was made while
the index was being updated and I don't see any indication of a crash.
Just for my clarification, if I update the index, but don't close the
IndexWriter (because I may need it again soon), can the index on disk
be left in an inconsistent state? Do I need to close the IndexWriter
to assure the index is OK in disk?
It is imperative I figure out what is going on. I can't take the risk
of my customer's data becoming corrupted due to my error.
Bill
On Apr 8, 2005, at 4:59 PM, Daniel Naber wrote:
> On Friday 08 April 2005 23:51, Bill Tschumy wrote:
>
>> Would
>> this happen if there was a Writer that was not closed?
>
> Either the copy was done while the index was being updated, or the
> previous
> index update didn't finish (e.g. because it crashed before the index
> was
> closed).
>
> Regards
> Daniel
>
> --
> http://www.danielnaber.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>
--
Bill Tschumy
Otherwise -- Austin, TX
http://www.otherwise.com
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic