lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <>
Subject [jira] Commented: (LUCENE-1076) Allow MergePolicy to select non-contiguous merges
Date Tue, 21 Jul 2009 18:48:14 GMT


Shai Erera commented on LUCENE-1076:

Well ... what I was thinking of is that even if the app does not care about internal doc IDs,
the Lucene code may very well care. If we don't shift doc IDs back, it means maxDoc will continue
to grow, and at some point (extreme case though), maxDoc will equal 1M, while there will be
just 50K docs in the index.

AFAIU, maxDoc is used today to determine array length in FieldCache, I've seen it used in
IndexSearcher to sort the sub readers (at least in the past) etc. So perhaps alongside maxDoc
we'll need to keep a curNumDocs member to track the actual number of documents?

But I have a feeling this will also get complicated.

> 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
>         Attachments: 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.
You can reply to this email to add a comment to the issue online.

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

View raw message