[
https://issues.apache.org/jira/browse/SOLR-10921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-10921:
--------------------------------
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.
was:
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.
> Make boolean query clause limit configurable per-query
> ------------------------------------------------------
>
> Key: SOLR-10921
> URL: https://issues.apache.org/jira/browse/SOLR-10921
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Yonik Seeley
> Fix For: master (7.0)
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
