[
https://issues.apache.org/jira/browse/LUCENE-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293611#comment-14293611
]
Shawn Heisey commented on LUCENE-4835:
--------------------------------------
I think the discussion here does leave room for an increase in the default
maxBooleanClauses value, just not to Integer.MAX_VALUE. Rob's objections to
that setting do have technical merit. My initial WAG as to a new value is
16384 ... that would satisfy the requirements of every situation I've actually
seen when Solr users must increase the value, but it would still be low enough
to catch seriously abnormal code/config.
I'm still pursuing SOLR-4586 to remove the limit entirely in Solr, though if we
increase the default in Lucene, the default in Solr should also get a bump.
> Raise maxClauseCount in BooleanQuery to Integer.MAX_VALUE
> ---------------------------------------------------------
>
> Key: LUCENE-4835
> URL: https://issues.apache.org/jira/browse/LUCENE-4835
> Project: Lucene - Core
> Issue Type: Improvement
> Affects Versions: 4.2
> Reporter: Shawn Heisey
> Fix For: 4.9, Trunk
>
>
> Discussion on SOLR-4586 raised the idea of raising the limit on boolean
> clauses from 1024 to Integer.MAX_VALUE. This should be a safe change. It
> will change the nature of help requests from "Why can't I do 2000 clauses?"
> to "Why is my 5000-clause query slow?"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
