[
https://issues.apache.org/jira/browse/LUCENE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483742
]
Steven Parkes commented on LUCENE-847:
--------------------------------------
Visibility is one of those things I haven't cleaned up yet.
Client code is gonna want to create and set merge policies. And it'll want to
set "external" merge policy parameters. That's all probably not controversial.
As for other stuff, I tend to leave things open, but I know that's debatable
and don't have a strong opinion in this case.
In fact, there a few things here that are fairly subtle/important. The
relationship/protocol between the writer and policy is pretty strong. This can
be seen in the strawman concurrent merge code where the merge policy holds
state and relies on being called from a synchronized writer method. If that
goes forward anything like it is, it would argue for tightening that api up
some. Chris suggested a way to make the writer<>polcy relationship "atomic". I
didn't add the code (yet) but I'm not against it.
> 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]
