It seems TooManyClauses is a potential problem for any query that expands to a series of OR'ed boolean queries (PrefixQuery, WildcardQuery, RangeQuery...). If the max was set too high, the inefficiency would make the search unsable.
I kind of worked around this by creating a BitSetQuery, and extended PrefixQuery and WildcardQuery so that they rewrite to BitSetQuery. This at least made both queries usable on a large index (~40mil documents) with acceptable speed, without the use of filters. I also extended QueryParser so it creates the new PrefixQuery and the new WildcardQuery instead of the ones provided by the distribution. Ray On 7/12/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > > Hi Mickaël, > > Take a look at the org.apache.lucene.search.DateFilter class that comes > with Lucene. This does date range filtering (I am using a modified version > of this class for filtering my date format). It should be relatively > strightforward to modify this for filtering numeric ranges. If your numbers > are stored as zero padded Strings then you should be able to leave the > bits() method as is otherwise you might have to put some String to number > conversion in there somewhere. > > Regards > > Paul I > > > > Rifflard Mickaël > <Mickael.Rifflard > @atosorigin.com> To > <java-user@lucene.apache.org> > 12/07/2005 09:31 cc > > Subject > Please respond to RE: Lucene and numerical fields > [EMAIL PROTECTED] search > apache.org > > > > > > > > > > Hi Paul, > > I have seen Filter feature and search how to use it to solve my problem > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
