[SOLR-10921] Make boolean query clause limit configurable per-query

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 7.0
• Assignee: Yonik Seeley
• Reporter: Yonik Seeley
• Created: 20/Jun/17 13:42
• Updated: 08/Jun/19 15:22
• Resolved: 22/Jun/17 20:06

Description

This is the Solr version of LUCENE-7880

Background: The removal of the arbitrary maxBooleanClauses has been blocked in SOLR-4586, and there were objections to adding the ability to override maxBooleanClauses at the Lucene level in LUCENE-7880.
That leaves us with this last option of implementing the check in solr by raising the lucene limit and then using the maxBooleanClauses from solrconfig.xml to throw an exception when the limit is exceeded. Solr QParsers have access to the request object, which knows the schema/core/config. This should fix the last-core-wins behavior due to the lucene limit being a static.

Although this enables controlling the limit on a per-query basis, this issue is not about adding any user API to do so. The capability will only be used to make the current Solr maxBooleanClauses setting truly per-solr-core rather than last-core-wins.

Issue Links

• is related to: SOLR-13336 solrconfig.xml maxBooleanClauses ignored by programtic/rewrtten queries; can result in exponential expansion of naive queries
• relates to: LUCENE-7880 Make boolean query clause limit configurable per-query
• relates to: SOLR-4586 Eliminate the maxBooleanClauses limit