with LUCENE-1860 there is no real need for this comment - reducing to core info

git-svn-id: https://svn.apache.org/repos/asf/lucene/java/trunk@808246 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Mark Robert Miller 2009-08-27 01:32:15 +00:00
parent d6431b34b3
commit 4e34506ba2
1 changed files with 2 additions and 11 deletions

View File

@ -51,18 +51,9 @@ public class BooleanQuery extends Query {
*/
public static int getMaxClauseCount() { return maxClauseCount; }
/** Set the maximum number of clauses permitted per BooleanQuery.
/**
* Set the maximum number of clauses permitted per BooleanQuery.
* Default value is 1024.
* <p>TermQuery clauses are generated from for example prefix queries and
* fuzzy queries. Each TermQuery needs some buffer space during search,
* so this parameter indirectly controls the maximum buffer requirements for
* query search.
* <p>When this parameter becomes a bottleneck for a Query one can use a
* Filter. For example instead of a {@link TermRangeQuery} one can use a
* {@link TermRangeFilter}.
* <p>Normally the buffers are allocated by the JVM. When using for example
* {@link org.apache.lucene.store.MMapDirectory} the buffering is left to
* the operating system.
*/
public static void setMaxClauseCount(int maxClauseCount) {
if (maxClauseCount < 1)