Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-10921

Make boolean query clause limit configurable per-query

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.0
    • Component/s: None
    • Labels:
      None

      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.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              yseeley@gmail.com Yonik Seeley
              Reporter:
              yseeley@gmail.com Yonik Seeley

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment