[
https://issues.apache.org/jira/browse/LUCENE-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847163#comment-15847163
]
ASF GitHub Bot commented on LUCENE-7671:
GitHub user kelaban opened a pull request:
https://github.com/apache/lucene-solr/pull/151
LUCENE-7671 - Enhance UpgradeIndexMergePolicy with additional options
Also updates Backwards compatibility tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kelaban/lucene-solr
jira/master/LUCENE-7671/upgrading-merge-policy
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/lucene-solr/pull/151.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #151
commit c0120745617cbd50a920338cb83e751b9a26963e
Author: Keith Laban
Date: 2017-01-25T17:08:22Z
LUCENE-7671 - Enhance UpgradeIndexMergePolicy with additional options
> 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
