Hmm... that's actually not true: RangeQuery will still throw that exception, unless you call setConstantScoreRewrite to true (at which point it does the same thing as ConstantScoreRangeQuery, ie that exception will not be thrown).
The javadoc for RangeQuery is very misleading. (This happened when we absorbed ConstantScoreRangeQuery into RangeQuery, for 2.4). I'll fix RangeQuery's javadoc. Mike On Wed, May 20, 2009 at 1:00 PM, Joel Halbert <j...@su3analytics.com> wrote: > Hi, > > Looking at the docs for the 2.4 codebase, for RangeQuery > http://lucene.apache.org/java/2_4_0/api/index.html?org/apache/lucene/search/RangeQuery.html > > there is a comment that a TooManyClauses exception is no longer thrown. > > Does this mean that it is now safe to use RangeQuery without worrying > about excessive term expansion? Has the implementation changed such that > it is no longer constructing multiple BooleanQuery terms to perform a > range query? > > Thx, > Joel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
