Hi,
That'd be great! I will post the code as is, hope to get feedbacks.
There are some problems with BitSetQuery by itself with MultiSearcher
due to different offsets, so it's in a bit of a mess right now, and
cannot work by itself unless used with a custom ParallelMultiSearcher.
However, It sho
I second the motion. It sounds like a good solution to TooManyClauses
exception.
-Original Message-
From: Otis Gospodnetic <[EMAIL PROTECTED]>
Sent: Jul 16, 2005 5:59 PM
To: java-user@lucene.apache.org, Ray Tsang <[EMAIL PROTECTED]>
Subject: Re: Lucene and numerical field
Hi Ray,
If you can share your BitSetQuery and QP modifications, feel free to
suggest them for inclusion to the core or contrib (by attaching them to
a new entry in Bugzilla).
Otis
--- Ray Tsang <[EMAIL PROTECTED]> wrote:
> It seems TooManyClauses is a potential problem for any query that
> exp
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 exte
I use ConstantScoreRangeQuery for this purpose:
http://issues.apache.org/bugzilla/show_bug.cgi?id=34673
-Yonik
On 7/12/05, Rifflard Mickaël <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm using Lucene as a fulltext search engine since a year now and this one
> works well for this.
> Now, I want t
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 yo
12 juillet 2005 10:16
À : java-user@lucene.apache.org
Objet : Re: Lucene and numerical fields search
I have similar requirements. To get around the "Too many clauses" problem I
am creating a Filter (this takes one or two seconds to create on an index
of around 25 documents)
I have similar requirements. To get around the "Too many clauses" problem I
am creating a Filter (this takes one or two seconds to create on an index
of around 25 documents) instead of using the RangeQuery. It's not ideal
but it does sidestep the problem. If you are using the same range in
