[
https://issues.apache.org/jira/browse/LUCENE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483929
]
Michael McCandless commented on LUCENE-847:
-------------------------------------------
Steven, I looked through the patch quickly. It looks great! First
some general comments and then I'll add more specifics as
separate comments.
Can you open separate issues for the other new and interesting merge
policies here? I think the refactoring of merge policy plus creation
of the default policy that is identical to today's merge policy, which
should be a fairly quick and low-risk operation, would then remain
under this issue?
Then, iterating / vetting / debugging the new interesting merge
policies can take longer under their own separate issues and time
frame.
On staging I think we could first do this issue (decouple MergePolicy
from writer), then LUCENE-845 because it blocks LUCENE-843 (which
would then be fixing LogarithmicMergePolicy to use segment sizes
instead of docs counts as basis for determing levels) then LUCENE-843
(performance improvements for how writer uses RAM)?
> Factor merge policy out of IndexWriter
> --------------------------------------
>
> Key: LUCENE-847
> URL: https://issues.apache.org/jira/browse/LUCENE-847
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Steven Parkes
> Assigned To: Steven Parkes
> Attachments: LUCENE-847.txt
>
>
> If we factor the merge policy out of IndexWriter, we can make it pluggable,
> making it possible for apps to choose a custom merge policy and for easier
> experimenting with merge policy variants.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
