[
https://issues.apache.org/jira/browse/SOLR-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved SOLR-2572.
-------------------------------
Resolution: Won't Fix
See my note on SOLR-2567, at the moment all merge policies take simple setters
with primitive types, so you can actually configure all their parameters
already.
Because of this, I think some factory interface would just be overkill, when
you can already just do:
{noformat}
<mergePolicy class="org.apache.lucene.index.TieredMergePolicy">
<int name="maxMergeAtOnceExplicit">19</int>
<int name="segmentsPerTier">9</int>
</mergePolicy>
{noformat}
> improve mergepolicy configuration
> ---------------------------------
>
> Key: SOLR-2572
> URL: https://issues.apache.org/jira/browse/SOLR-2572
> Project: Solr
> Issue Type: Improvement
> Reporter: Robert Muir
> Fix For: 3.3, 4.0
>
>
> Spinoff from SOLR-2567.
> Currently configuration of a mergepolicy in solr is by lucene classname (must
> have no-arg ctor), and
> some merge-policy specific configuration parameters are not per-mergepolicy,
> but instead with the rest of the index configuration.
> I think we should make this more pluggable, so that we can fully configure
> things like TieredMergePolicy,
> and also so that if someone wants to plug in their own MP they can do that
> too.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
