[
https://issues.apache.org/jira/browse/SOLR-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199945#comment-13199945
]
Jan Høydahl commented on SOLR-3093:
-----------------------------------
Yea, we'll go for a WARN for these ones. Besides, it *is* nice that it's
possible to drop-in upgrade war without upgrading config.
Then when/if proper xsd validation comes around (SOLR-1758), I guess we'll need
to tackle this and other similar cases again.
> Remove unused features <boolTofilterOptimizer> and <HashDocSet>
> ---------------------------------------------------------------
>
> Key: SOLR-3093
> URL: https://issues.apache.org/jira/browse/SOLR-3093
> Project: Solr
> Issue Type: Improvement
> Reporter: Jan Høydahl
> Fix For: 3.6, 4.0
>
>
> SolrConfig.java still tries to parse <boolTofilterOptimizer>
> But the only user of this param was SolrIndexSearcher.java line 366-381 which
> is commented out.
> Probably the whole logic should be ripped out, and we fail hard if we find
> this config option in solrconfig.xml
> Also, the <HashDocSet> config option is old and no longer used or needed?
> There is some code which tries to use it but I believe that since 1.4 there
> are more efficient ways to do the same. Should we also fail-fast if found in
> config or only print a warning?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
