[
https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603770#comment-13603770
]
Mark Miller commented on SOLR-4586:
-----------------------------------
Yup - that's the one.
I tried finding a jira issue i was involved in from years ago about this
setting, but couldn't dig it/them up.
We worked hard to limit the problems it was causing lucene and solr users. I
think it's kind of a crappy setting, always have, and it used to be a very
common pain point before things got better.
Anywhere sane should be using multi term queries that switch over to contant
score and don't have this limitation.
What did you do to trip this Shawn?
> Remove maxBooleanClauses from Solr
> ----------------------------------
>
> Key: SOLR-4586
> URL: https://issues.apache.org/jira/browse/SOLR-4586
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 4.2
> Reporter: Shawn Heisey
> Attachments: SOLR-4586.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 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
