[
https://issues.apache.org/jira/browse/SOLR-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931913#action_12931913
]
Lance Norskog edited comment on SOLR-2212 at 11/14/10 5:45 PM:
---------------------------------------------------------------
Also, it expects you to tell it whether to use compound files.
This signature structure just plain does not work with the solrconfig.xml
structure. The fact that the merge policy has to embed whether to use compound
files seems like an information leakage anyway. The MergePolicy returns lists
of segments, that's it. Knowing whether to use compound files is extraneous to
its mission.
was (Author: lancenorskog):
Also, it expects you to tell it whether to use compound files.
This signature structure just plain does not work with the solrconfig.xml
structure. The fact that the merge policy has to embed whether to use compound
files seems like an information leakage anyway. The MergePolicy returns lists
of segments, that's it. Adding whether to use compound files is extraneous and
in this case causes problems.
> NoMergePolicy class does not load
> ---------------------------------
>
> Key: SOLR-2212
> URL: https://issues.apache.org/jira/browse/SOLR-2212
> Project: Solr
> Issue Type: Bug
> Components: multicore
> Affects Versions: 3.1, 4.0
> Reporter: Lance Norskog
>
> Solr cannot use the Lucene NoMergePolicy class. It will not instantiate
> correctly when loading the core.
> Other MergePolicy classes work, including the BalancedSegmentMergePolicy.
> This is in trunk and 3.x.
--
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]
