: } else if (mergeFactor != -1) {
: log.warn("Use of <mergeFactor> cannot be configured if merge policy
: is not an instance of LogMergePolicy or TieredMergePolicy. The configured
: policy's defaults will be used.");
: }
:
: But still, I think it's better if it is a merge policy parameter. Then
: users don't even have to wonder why they see these messages in the log.
It can me a merge policy property -- buildMergePolicy ends with a call to
"SolrPluginUtils.invokeSetters" as a way to support any simple setter on
any (custom) merge policy ... so <int name="mergeFactor">10</int> should
work fine if th selected merge policy has a "setMergeFactor(int)" method.
the use of an explicit <mergeFactor> is just there for backcompat.
If the docs / sample configs are still promoting/suggesting <mergeFactor>
then that's just a doc bug.
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
