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 RangeQuery} one can use a /// {@link RangeFilter}. ///
Normally the buffers are allocated by the JVM. When using for example /// {@link Lucene.Net.store.MMapDirectory} the buffering is left to /// the operating system. ///
/// By default no optional clauses are neccessary for a match /// (unless there are no required clauses). If this method is used, /// then the specified numebr of clauses is required. ///
////// Use of this method is totally independant of specifying that /// any specific clauses are required (or prohibited). This number will /// only be compared against the number of matching optional clauses. ///
////// EXPERT NOTE: Using this method will force the use of BooleanWeight2, /// regardless of wether setUseScorer14(true) has been called. ///
/// ///o
is equal to this.