[
https://issues.apache.org/jira/browse/LUCENE-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603862#comment-13603862
]
Mark Miller commented on LUCENE-4835:
-------------------------------------
If that was really a concern - which for me, it wouldn't really be until I
started seeing the reports - but even if it's your concern, a huge limit still
would be much better. There is not really anything special about the fairly low
current value.
Im no so worried about this type of thing...you might think that you want every
hit back no matter what and ask for like the top 1 million hits and require a
huge pq and blow our your ram and oh how confusing...but people seem to get by
without us throwing arbitrary exceptions.
> 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: [email protected]
For additional commands, e-mail: [email protected]
