Also, over time, as segments that have marked deletions are merged,
> the disk space is also reclaimed.
>
> Mike
>
> dan at gmail wrote:
>
>>
>> Hello,
>>
>> Could someone please confirm that calling indexWriter.optimize() is
>> th
Hello,
Could someone please confirm that calling indexWriter.optimize() is the only
way to clean out the deleted documents from the disk?
I understand that indexWriter.deleteDocuments() does not clean the disk
space, and I tested that calling after indexWriter.flush() and
indexWriter.close() aft
est I can tell, you really
> can't be sure so downgrading is the safest course of action.
>
> Mike
>
> dan at gmail wrote:
>
>>
>> Hello,
>>
>> I don't have a good understanding of what options for avoid this
>> corrupted
>> in
I can tell, you really
> can't be sure so downgrading is the safest course of action.
>
> Mike
>
> dan at gmail wrote:
>
>>
>> Hello,
>>
>> I don't have a good understanding of what options for avoid this
>> corrupted
>> in
Hello,
I don't have a good understanding of what options for avoid this corrupted
index problem described in LUCENE-1282. It seems to me that I either
downgrade JRE from 1.6.0_06 to 1.6.0_03, or wait for an official release of
Lucene 2.4.0 which includes a workaround for this JRE bug.
http://is
