[
https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629052#comment-13629052
]
Jack Krupansky edited comment on SOLR-4586 at 4/11/13 4:06 PM:
---------------------------------------------------------------
{blockquote}
is there a way in Lucene to specify something like the following query (using
all of the different kinds of boolean logic) without BooleanQuery?
{code}
(+author:tolkien -title:hobbit) isbn:( ... 200000 different ISBNs ...)
{code}
{blockquote}
Sure, just break it up into 1024-term chunks:
{code}
(+author:tolkien -title:hobbit) isbn:( ( ... 1024 ISBNs ... ) ( ... 1024 ISBNs
...) ... repeat 200 times ... )
{code}
The parentheses for the sub-queries should cause the query parser to generate a
nested BooleanQuery for each sub-query.
was (Author: jkrupan):
{bq}
is there a way in Lucene to specify something like the following query (using
all of the different kinds of boolean logic) without BooleanQuery?
{code}
(+author:tolkien -title:hobbit) isbn:( ... 200000 different ISBNs ...)
{code}
{bq}
Sure, just break it up into 1024-term chunks:
{code}
(+author:tolkien -title:hobbit) isbn:( ( ... 1024 ISBNs ... ) ( ... 1024 ISBNs
...) ... repeat 200 times ... )
{code}
The parentheses for the sub-queries should cause the query parser to generate a
nested BooleanQuery for each sub-query.
> 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: [email protected]
For additional commands, e-mail: [email protected]
