You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2016/11/22 22:54:59 UTC
[jira] [Comment Edited] (SOLR-4586) Eliminate the maxBooleanClauses
limit
[ https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687572#comment-15687572 ]
Yonik Seeley edited comment on SOLR-4586 at 11/22/16 10:54 PM:
---------------------------------------------------------------
One step in the right direction... SOLR-9786 now produces TermsQueries (and hence avoids the maxBooleanClauses limit) from strings or numerics when called from a filter context.
So something like fq=foo_s:(term1 term2 term3 ... term2000) should now work.
I added a modified test from this JIRA (TestSolrQueryParser.testManyClauses) that changed the "q" to an "fq".
was (Author: yseeley@gmail.com):
One step in the right direction... SOLR-4586 now produces TermsQueries (and hence avoids the maxBooleanClauses limit) from strings or numerics when called from a filter context.
So something like fq=foo_s:(term1 term2 term3 ... term2000) should now work.
I added a modified test from this JIRA (TestSolrQueryParser.testManyClauses) that changed the "q" to an "fq".
> Eliminate the maxBooleanClauses limit
> -------------------------------------
>
> 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
> Fix For: 5.2, 6.0
>
> Attachments: SOLR-4586.patch, SOLR-4586.patch, SOLR-4586.patch, SOLR-4586.patch, SOLR-4586.patch, SOLR-4586.patch, SOLR-4586_verify_maxClauses.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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org