lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-7671) Enhance UpgradeIndexMergePolicy with additional options
Date Sun, 02 Apr 2017 19:52:41 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952832#comment-15952832
] 

Michael McCandless commented on LUCENE-7671:
--------------------------------------------

Hi [~k317h], thank you.  To fix the failing test, can you change it to use the version of
{{IndexWriter.addIndexes}} that takes {{CodecReader[]}} instead?  This should have the same
effect (some old, some new segments in one index).

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message