Sounds good. Thanks for all the help.
Shawn.
-Original Message-
From: Paul Elschot [mailto:[EMAIL PROTECTED]
Sent: Monday, September 20, 2004 4:22 PM
To: [EMAIL PROTECTED]
Subject: Re: Too many boolean clauses
On Monday 20 September 2004 20:54, Shawn Konopinsky wrote:
> Hey P
On Monday 20 September 2004 20:54, Shawn Konopinsky wrote:
> Hey Paul,
>
...
>
> Also - we are using a pooling feature which contains a pool of
> IndexSearchers that are used and tossed back each time we need to search.
> I'd hate to have to work around this and open up an IndexReader for this
> pa
On Monday 20 September 2004 20:54, Shawn Konopinsky wrote:
> Hey Paul,
>
> Thanks for the quick reply. Excuse my ignorance, but what do I do with the
> generated BitSet?
You can return it in in the bits() method of the object implementing your
org.apache.lucene.search.Filter (http://jakarta.apache
up an IndexReader for this
particular search, where all other searches use the pool. Suggestions?
Thanks,
Shawn.
-Original Message-
From: Paul Elschot [mailto:[EMAIL PROTECTED]
Sent: Monday, September 20, 2004 12:51 PM
To: Lucene Users List
Subject: Re: Too many boolean clauses
On Mond
ut 500,000 unique ids. If I want to
> query all records with ids [1-2000], I build a boolean query containing
> all the numbers in the range. eg. id:(1 2 3 ... 1999 2000)
>
> The problem with this is that I get the following error :
> org.apache.lucene.queryParser.ParseException: Too m
query containing all
the numbers in the range. eg. id:(1 2 3 ... 1999 2000)
The problem with this is that I get the following error :
org.apache.lucene.queryParser.ParseException: Too many boolean clauses
Any ideas on how I might circumvent this issue by either finding a way to
rewrite the query, or
Thanks, I will look at the sorting code. Sorting results by date is
next on list. For now, I only have a small number of documents but the
set is to grow to over 8 million documents for the collection I am
working on. Another collection we have is 40 million documents or so.
From what you
Claude Devarenne writes:
> Hi,
>
> I have over 60,000 documents in my index which is slightly over a 1 GB
> in size. The documents range from the late seventies up to now. I
> have indexed dates as a keyword field using a string because the dates
> are in MMDD format. When I do range que
On May 18, 2004, at 3:56 PM, Claude Devarenne wrote:
Thanks, I'll try that. It would nice too if I could extend field (it
is a final class) and create a numerical field. Is that not
desirable?
It isn't that much more effort to have something like NumberUtils
listed here:
http://wiki.apache.or
> Is there a simpler, easier way to do this?
Yes. I have started implementing a "QuickRangeQuery" class, that doesn't
have the BooleanQuery limitation, but scores every matching document as 1.0.
I will see if I can get it finished in the next 24 hours, and post back
to this thread.
=Matt
PS: I'
Thanks, I'll try that first and then Ype's suggestion if necessary. I
have been shying away from filters so now I have no excuse ;-)
Claude
On May 18, 2004, at 1:35 PM, Andy Goodell wrote:
In our application we had a similar problem with non-date ranges until
we realized that it wasnt so much th
In our application we had a similar problem with non-date ranges until
we realized that it wasnt so much that we were searching for the
values in the range as restricting the search to that range, and then
we used an extension to the org.apache.lucene.search.Filter class, and
our implementation got
Thanks, I'll try that. It would nice too if I could extend field (it
is a final class) and create a numerical field. Is that not desirable?
Claude
On May 18, 2004, at 12:06 PM, Ype Kingma wrote:
On Tuesday 18 May 2004 19:38, Claude Devarenne wrote:
Hi,
I have over 60,000 documents in my index w
On Tuesday 18 May 2004 19:38, Claude Devarenne wrote:
> Hi,
>
> I have over 60,000 documents in my index which is slightly over a 1 GB
> in size. The documents range from the late seventies up to now. I
> have indexed dates as a keyword field using a string because the dates
> are in MMDD for
Hi,
I have over 60,000 documents in my index which is slightly over a 1 GB
in size. The documents range from the late seventies up to now. I
have indexed dates as a keyword field using a string because the dates
are in MMDD format. When I do range queries things are OK as long
as I don't
15 matches
Mail list logo
