[
https://issues.apache.org/jira/browse/LUCENE-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096793#comment-14096793
]
Uwe Schindler edited comment on LUCENE-5883 at 8/14/14 9:39 AM:
----------------------------------------------------------------
+1, very good!
I think LUCENE-5526 is not obsolete by that, but much easier to implement. I
still would like to pass a MergePolicy to forceMerge, just for the forced
merging.
On the other hand, you can change merge policy, forceMerge() without waiting,
and change back. This is possible, because the merge policy does not change for
running merges...
was (Author: thetaphi):
+1, very good!
I think LUCENE-5526 is not obsolete by that, but much easier to implement. I
still would like to pass a MergePolicy to forceMerge, just for the forced
merging.
> 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]
