lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Commented] (SOLR-4586) Eliminate the maxBooleanClauses limit
Date Fri, 07 Nov 2014 21:01:34 GMT


Michael McCandless commented on SOLR-4586:

bq. Robert Muir now has a conflict-of-interest that he didn't have at the time he voted.

Please don't make such unhelpful blanket statements.

In fact, we all have on-paper conflicts of interest here, different
motivations for favoring one change over another, etc., but then we
trust one another to wear the right hat at the right time and to do
what we feel is best for the project.  Each of us argues our point of
view on issues such as this based on technical merit/tradeoffs of the
different approaches.

> Eliminate the maxBooleanClauses limit
> -------------------------------------
>                 Key: SOLR-4586
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 4.2
>         Environment: 4.3-SNAPSHOT 1456767M - ncindex - 2013-03-15 13:11:50
>            Reporter: Shawn Heisey
>         Attachments: SOLR-4586.patch, SOLR-4586.patch, SOLR-4586.patch, SOLR-4586.patch,
SOLR-4586.patch, SOLR-4586.patch, SOLR-4586_verify_maxClauses.patch
> In the #solr IRC channel, I mentioned the maxBooleanClauses limitation to someone asking
a question about queries.  Mark Miller told me that maxBooleanClauses no longer applies, that
the limitation was removed from Lucene sometime in the 3.x series.  The config still shows
up in the example even in the just-released 4.2.
> Checking through the source code, I found that the config option is parsed and the value
stored in objects, but does not actually seem to be used by anything.  I removed every trace
of it that I could find, and all tests still pass.

This message was sent by Atlassian JIRA

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

View raw message