From 4e34506ba253d96de4178d32d97c130d3cb03be3 Mon Sep 17 00:00:00 2001 From: Mark Robert Miller Date: Thu, 27 Aug 2009 01:32:15 +0000 Subject: [PATCH] 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 --- src/java/org/apache/lucene/search/BooleanQuery.java | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/src/java/org/apache/lucene/search/BooleanQuery.java b/src/java/org/apache/lucene/search/BooleanQuery.java index 6028d602847..4c2e3471a35 100644 --- a/src/java/org/apache/lucene/search/BooleanQuery.java +++ b/src/java/org/apache/lucene/search/BooleanQuery.java @@ -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. - *

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. - *

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}. - *

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)