lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Hostetter <>
Subject Re: svn commit: r332747 - in /lucene/java/trunk: ./ src/java/org/apache/lucene/search/regex/ src/test/org/apache/lucene/search/regex/
Date Wed, 16 Nov 2005 18:51:33 GMT

: > Should we dynamically decide to switch to FieldNormQuery when
: > BooleanQuery.maxClauseCount is exceeded?  That way queries that

: Why not leave that decision to the program using the query?
: Something like this:
: - catch the TooManyClauses exception,
: -  adapt (the offending parts of) the query to make these use
:    a FieldNormQuery,
: - retry with a warning to the provider of the query that

...because it seems like the people who typically run into TooManyClauses
aren't familiary with whole API enough to understand why they are getting
the exception.  right now they ask questions and people give them advice
on reducing clauses based on their specific use case.  If this change were
made the advice could be simplified and generalized - but the number of
confused questions probably wouldn't decrease that much.

I think Doug is suggesting that the "default" case for people who don't
look very deeply at the API is to "just work" all of the time, as best it
can.  people who dig deeper can call the method or set the property to
make it fail in the extreme cases where they want it to fail.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message