[
https://issues.apache.org/jira/browse/LUCENE-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603850#comment-13603850
]
Mark Miller commented on LUCENE-4835:
-------------------------------------
bq. it would change the natural of help requests from "why did i get
TooManyClauses exception" to "why did i get super-strange exception: is this a
bug?"
It would remove even more of those silly "why did I get TooManyClauses
exception" questions that tons can still get at 1024 or whatever it is. How
many people will what your talking about bite? That many explicit bq's? Well
that one in a million guy will bring his expcetion to the list and mention, oh,
im doing 5 billion boolean clauses or whatever.
This silly artificial limit hasnt even kept pace with hardware improvements
over the years :) Not that it matters - it's arbitrary anyway.
> 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: 5.0, 4.3
>
>
> 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 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
