lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <>
Subject [jira] [Updated] (LUCENE-1076) Allow MergePolicy to select non-contiguous merges
Date Tue, 03 May 2011 12:09:03 GMT


Shai Erera updated LUCENE-1076:

    Attachment: LUCENE-1076-3x.patch

Patch against 3x. This is not ready to commit yet, as many tests fail on exceptions like this:

    [junit] java.lang.IndexOutOfBoundsException
    [junit]     at java.util.AbstractList.subList(
    [junit]     at java.util.Vector.subList(
    [junit]     at org.apache.lucene.index.IndexWriter.commitMerge(
    [junit]     at org.apache.lucene.index.IndexWriter.mergeMiddle(
    [junit]     at org.apache.lucene.index.IndexWriter.merge(

Mike says there was  an earlier commit (handled how deletes are flushed) that is a dependency
of that, and that I can continue only he back-ports that.

In the meantime, I've fixed tests that assumed LogMP (for setting compound and mergeFactor)
by adding LTC.setUseCompoundFile and LTC.setMergeFactor as utility methods.

Will continue after Mike back-ports the dependencies.

> Allow MergePolicy to select non-contiguous merges
> -------------------------------------------------
>                 Key: LUCENE-1076
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>    Affects Versions: 2.3
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 3.2, 4.0
>         Attachments: LUCENE-1076-3x.patch, LUCENE-1076.patch, LUCENE-1076.patch, LUCENE-1076.patch
> I started work on this but with LUCENE-1044 I won't make much progress
> on it for a while, so I want to checkpoint my current state/patch.
> For backwards compatibility we must leave the default MergePolicy as
> selecting contiguous merges.  This is necessary because some
> applications rely on "temporal monotonicity" of doc IDs, which means
> even though merges can re-number documents, the renumbering will
> always reflect the order in which the documents were added to the
> index.
> Still, for those apps that do not rely on this, we should offer a
> MergePolicy that is free to select the best merges regardless of
> whether they are continuguous.  This requires fixing IndexWriter to
> accept such a merge, and, fixing LogMergePolicy to optionally allow
> it the freedom to do so.

This message is automatically generated by JIRA.
For more information on JIRA, see:

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

View raw message