lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tommaso Teofili (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-2983) Unable to load custom MergePolicy
Date Thu, 22 Mar 2012 07:14:24 GMT


Tommaso Teofili commented on SOLR-2983:

I just noticed also the toIndexWriter method should be explicitly tested, going to work on
it and attach a new patch
> Unable to load custom MergePolicy
> ---------------------------------
>                 Key: SOLR-2983
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Mathias Herberts
>            Assignee: Tommaso Teofili
>            Priority: Minor
>             Fix For: 3.6, 4.0
>         Attachments: SOLR-2983.patch
> As part of a recent upgrade to Solr 3.5.0 we encountered an error related to our use
of LinkedIn's ZoieMergePolicy.
> It seems the code that loads a custom MergePolicy was at some point moved into
from, but as this code was copied verbatim it now contains a bug:
>     try {
>       policy = (MergePolicy) schema.getResourceLoader().newInstance(mpClassName, null,
new Class[]{IndexWriter.class}, new Object[]{this});
>     } catch (Exception e) {
>       policy = (MergePolicy) schema.getResourceLoader().newInstance(mpClassName);
>     }
> 'this' is no longer an IndexWriter but a SolrIndexConfig, therefore the call to newInstance
will always throw an exception and the catch clause will be executed. If the custom MergePolicy
does not have a default constructor (which is the case of ZoieMergePolicy), the second attempt
to create the MergePolicy will also fail and Solr won't start.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message