lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grant Ingersoll <gsing...@apache.org>
Subject Re: lucene-core-2.2.0.jar broken? CorruptIndexException?
Date Thu, 29 Nov 2007 20:53:50 GMT

On Nov 29, 2007, at 2:26 PM, Bill Janssen wrote:

>> Are you still getting the original exception too or just the Array  
>> out =20=
>>
>> of bounds one now?  Also, are you doing anything else to the index  
>> =20
>> while this is happening?  The code at the point in the exception  
>> below =20=
>>
>> is trying to properly handle deleted documents.
>
> Just the array-out-of-bounds one, now.  The current version of the
> code creates a writer, then deletes all old Lucene 'Document'
> instances belonging to the specified UpLib doc-id, using that writer,
> then re-indexes that UpLib doc-id (which consists of one-to-N Lucene
> 'Document's).  After doing the six UpLib documents, it calls
> optimize().

I'm curious what happens if you call optimize after doing the deletion  
but before the re-indexing.

Also, could you try out the CheckIndex tool in 2.3-dev before and  
after the deletes?

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message