[
https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611537#comment-13611537
]
Shawn Heisey commented on SOLR-4586:
------------------------------------
Yes, it has morphed quite a lot. I had some fundamental misunderstandings
early on. I suppose a true long-term goal would be to have Solr stop creating
BooleanQuery objects whenever possible and use newer query objects. I don't
know enough about the low-level details to know if that IS possible.
In the 4.x short term, we probably need to support setting a low limit as
mentioned in existing configs, and set a high limit if it's not configured.
That's what I've attempted to do in the newest patches.
Exactly what to do for 5.x and beyond is something I'm not sure about. If
we're going to support a user setting a low limit, Robert's idea of putting it
into solr.xml or its replacement strikes me as the right thing to do. We could
also set a very high limit and not let the user configure it.
Is there any consensus to be found here?
> Increase default maxBooleanClauses
> ----------------------------------
>
> Key: SOLR-4586
> URL: https://issues.apache.org/jira/browse/SOLR-4586
> 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
>
>
> 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
