: > You mean Theoritically
: > RangeQuery should be forbidden because it always has potential time bomb ?
: > Should we comment it in javadoc ?
In my opinion, the only reason to use RangeQuery is if you are dealing
with very controlled ranges, where you know hte number of terms it will
expand to
Hello,
> >
> > : I upgade to 1.9.1 and reindexing
> > : I used NumberTool when I index the number.
> > :
> > : after upgrade I got following error when number range query.
> > : with query
> >
> > The possibility of a TooManyClauses exception has always existed with
> > RangeQuery and numbers, e
Hello
- Original Message -
From: "Chris Hostetter" <[EMAIL PROTECTED]>
To: "Lucene Users"
Sent: Tuesday, March 07, 2006 3:49 PM
Subject: Re: BooleanQuery$TooManyClauses with 1.9.1 when Number RangeQuery
>
> : I upgade to 1.9.1 and reindexing
> :
: I upgade to 1.9.1 and reindexing
: I used NumberTool when I index the number.
:
: after upgrade I got following error when number range query.
: with query
The possibility of a TooManyClauses exception has always existed with
RangeQuery and numbers, even when using NumberTool. Even if you neve
Hello
I upgade to 1.9.1 and reindexing
I used NumberTool when I index the number.
after upgrade I got following error when number range query.
with query
2006-03-07 09:08:03,216 [TP-Processor3] DEBUG
com.nannet.jettiger.util.word.JetTigerAdapter - Queryafter=+prntid:56
+(+(+attid:113 +[0
