I thought the purpose of this method was for applications to specify the largest possible BooleanQuery that could be created in their application (either progromaticaly, via QueryParser, or as a result of rewriting a non-primative).
Changing this to be non-static would (besides breaking existing applications) leave apps with no way to limit the number of clauses generated "under the covers". : Date: Tue, 10 Jan 2006 18:36:33 -0800 (PST) : From: Otis Gospodnetic <[EMAIL PROTECTED]> : Reply-To: java-dev@lucene.apache.org, : Otis Gospodnetic <[EMAIL PROTECTED]> : To: java-dev@lucene.apache.org : Subject: BooleanQuery: static setMaxClauseCount(int)? : : Hi, : : Is there a reason this method is static? : : public static void setMaxClauseCount(int maxClauseCount) : If not, I'll change it. : : Thanks, : Otis : : : : --------------------------------------------------------------------- : To unsubscribe, e-mail: [EMAIL PROTECTED] : For additional commands, e-mail: [EMAIL PROTECTED] : -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
