[ https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael McCandless updated LUCENE-1076: --------------------------------------- Attachment: LUCENE-1076.patch Phew, this patch almost fell below the event horizon of my TODO list... I'm attaching new modernized one. I also mod'd the policy to not select two max-sized merges at once. I think it's ready to commit... > Allow MergePolicy to select non-contiguous merges > ------------------------------------------------- > > Key: LUCENE-1076 > URL: https://issues.apache.org/jira/browse/LUCENE-1076 > 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.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: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org