[ https://issues.apache.org/jira/browse/LUCENE-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933483#comment-15933483 ]
Keith Laban commented on LUCENE-7671: ------------------------------------- Pushed a new version that breaks out the behavior outlined above into a new class called {{LiveUpgradeIndexMergePolicy}}. The name indicates that a different IndexWriter need not be used. Additionally, because the new MP does not have an option to ignore new segments, I've changed the IndexUpgrader script to accept an additional parameter telling it to "include-new-segments" allowing the switch between the old behavior and new behavior. The test are randomized between old/new behavior for coverage. > Enhance UpgradeIndexMergePolicy with additional options > ------------------------------------------------------- > > Key: LUCENE-7671 > URL: https://issues.apache.org/jira/browse/LUCENE-7671 > Project: Lucene - Core > Issue Type: Improvement > Reporter: Keith Laban > > Enhance UpgradeIndexMergePolicy to be a MergePolicy that can be used outside > the scope the IndexUpgrader. > The enhancement aims to allow the UpgradeIndexMergePolicy to: > 1) Delegate normal force merges to the underlying merge policy > 2) Enable a flag that will explicitly tell UpgradeIndexMergePolicy when it > should start looking for upgrades. > 3) Allow new segments to be considered to be merged with old segments, > depending on underlying MergePolicy. > 4) Be configurable for backwards compatibility such that only segments > needing an upgrade would be considered when merging, no explicit upgrades. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org