lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Resolved] (SOLR-3093) Decide destiny of LuceneQueryOptimizer (solrconfig.xml: <boolTofilterOptimizer>)
Date Fri, 31 Aug 2012 06:15:07 GMT


Hoss Man resolved SOLR-3093.

       Resolution: Fixed
    Fix Version/s:     (was: 4.0)
         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:
>             Project: Solr
>          Issue Type: Task
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>            Priority: Minor
>             Fix For: 4.0-ALPHA, 3.6
> still tries to parse <boolTofilterOptimizer>
> But the only user of this param was 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 {{, 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:

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

View raw message