lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ning Li (JIRA)" <>
Subject [jira] Commented: (LUCENE-672) new merge policy
Date Sat, 16 Sep 2006 03:47:23 GMT
    [ ] 
Ning Li commented on LUCENE-672:

A small fix named KeepDocCount0Segment.Sept15.patch is attached to LUCENE-565 (can't attach

In mergeSegments(...), if the doc count of a merged segment is 0, it is not added to the index
(it should be properly cleaned up). Before LUCENE-672, a merged segment was always added to
the index. The use of mergeSegments(...) in, e.g. addIndexes(Directory[]), assumed that behaviour.
For code simplicity, this fix restores the old behaviour that a merged segment is always added
to the index. This does NOT break any of the good properties of the new merge policy.

TestIndexWriterMergePolicy is slightly modified to fix a bug and to check that segments are
probably cleaned up. The patch passes all the tests.

> new merge policy
> ----------------
>                 Key: LUCENE-672
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: Index
>    Affects Versions: 2.0.0
>            Reporter: Yonik Seeley
>         Assigned To: Yonik Seeley
>             Fix For: 2.1
> New merge policy developed in the course of 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message