[
https://issues.apache.org/jira/browse/SOLR-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-3093.
----------------------------
Resolution: Fixed
Fix Version/s: (was: 4.0)
3.6
4.0-ALPHA
Assignee: Jan Høydahl (was: Mark Miller)
As Jan noted in his comment, this was ultimately dealt with in SOLR-1052 -
r1308608 adds a SolrConfig check if boolTofilterOptimizer is specified and if
it is, logs a warning that it has no effect.
> Decide destiny of LuceneQueryOptimizer (solrconfig.xml:
> <boolTofilterOptimizer>)
> --------------------------------------------------------------------------------
>
> Key: SOLR-3093
> URL: https://issues.apache.org/jira/browse/SOLR-3093
> Project: Solr
> Issue Type: Task
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Minor
> Fix For: 4.0-ALPHA, 3.6
>
>
> SolrConfig.java still tries to parse <boolTofilterOptimizer>
> But the only user of this param was SolrIndexSearcher.java line 366-381 which
> is commented out since 3.1.
> From Solr3.6 we print a warning if we find this option is found in
> solrconfig.xml (SOLR-1052):
> {noformat}
> WARN: solrconfig.xml: <boolTofilterOptimizer> is currently not implemented
> and has no effect.
> {noformat}
> However, the dead, commented code is still in place in {{SolrConfig.java,
> SolrIndexSearcher.Java}}. We should decide what do do, either re-implement
> boolTofilterOptimizer or remove it completely.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
