[
https://issues.apache.org/jira/browse/LUCENE-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096603#comment-14096603
]
Shai Erera commented on LUCENE-5883:
------------------------------------
BTW, the way I implemented it is that top-level API methods grab the current
MergePolicy on the IWC and pass it down to methods like mergeMiddle(),
commitInternal() etc., so that if the MP changes in the middle, nothing weird
happens. E.g. if a merge was registered, but midway the MP changes and its CFS
settings are different ... I think it's safer and it's not important to have
THE most recent MP affect already registered merges.
> Move MergePolicy to LiveIndexWriterConfig
> -----------------------------------------
>
> Key: LUCENE-5883
> URL: https://issues.apache.org/jira/browse/LUCENE-5883
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/index
> Reporter: Shai Erera
> Assignee: Shai Erera
> Attachments: LUCENE-5883.patch, LUCENE-5883.patch
>
>
> Since LUCENE-5711, MergePolicy is no longer wired to an IndexWriter instance.
> Therefore it can be moved to be a live setting on IndexWriter, which will
> allow apps to plug-in an MP on a live IW instance, without closing/reopening
> the writer. See for example LUCENE-5526 - instead of adding MP to forceMerge,
> apps could change the MP before calling forceMerge, with e.g. an
> UpgradeIndexMergePolicy.
> I think we can also make MergeScheduler a live setting, though I currently
> don't see the benefits of doing that, so I'd rather not touch it now.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
