[
https://issues.apache.org/jira/browse/LUCENE-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949261#comment-15949261
]
Keith Laban commented on LUCENE-7671:
-------------------------------------
[~mikemccand] I updated PR with some extra changes:
- Fixed typo in testUpgradeWithExcplicitUpgrades
- Added usage for -include-new-segments options
- Also added -num-segments option for IndexUpgrader and usage
- Added random toggle for new options to be added in tests
Still outstanding: See my earlier
[comment|https://issues.apache.org/jira/browse/LUCENE-7671?focusedCommentId=15925030&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15925030]
about the failing test.
> 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: [email protected]
For additional commands, e-mail: [email protected]
