This is what I have been doing with DateFilter
DateFilter dateFilter = new DateFilter("published", lLimitDate,
System.currentTimeMillis());
TopFieldDocs docs = searcher.search(parser.parse(sSearchPhrase), dateFilter,
utility.iMaxResults, new Sort(sortFields));
Ed
--- Luke Francl <[EMAIL PROT
On Tue, 2004-11-16 at 16:32, Paul Elschot wrote:
> Once you approach 1000 days, you'll get the same problem again,
> so you might want to use a filter for the dates.
> See DateFilter and the archives on MMDD.
Can anyone point to a good example of how to use the DateFilter?
Thanks,
Luke
---
On Tuesday 16 November 2004 21:35, Joe Krause wrote:
> Hey Folks, I just inherited a deployed Lucene based application that
> started throwing the following exception:
>
> org.apache.lucene.search.BooleanQuery$TooManyClauses
...
> I did some research regarding this error and found out that the def
Hey Folks, I just inherited a deployed Lucene based application that
started throwing the following exception:
org.apache.lucene.search.BooleanQuery$TooManyClauses
at
org.apache.lucene.search.BooleanQuery.add(BooleanQuery.java:79)
at
org.apache.lucene.search.BooleanQuery.add(Boolea
t: RE: BooleanQuery - TooManyClauses
Even if you need to be able to search on ranges that include the time,
you could benefit from adding a few extra fields to your documents.
For example: add a year field and an hour field:
If the user then specifies a range between 2001-08-10 11:00 and
2004-10-
You can already add the separate fields to your documents even if you
don't use them yet...
Regards,
Luc
> -Original Message-
> From: Terry Steichen [mailto:[EMAIL PROTECTED]
> Sent: dinsdag 26 oktober 2004 18:28
> To: Lucene Users List
> Subject: Re: BooleanQu
Terry Steichen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 26, 2004 11:28 AM
To: Lucene Users List
Subject: Re: BooleanQuery - TooManyClauses
I think what Erik's asking is whether you can live with expressing your
indexed date in the form of MMDD, without the hour and minute
extension.
for more robust solution but this should do for now.
Thanks,
Ross
-Original Message-
From: Terry Steichen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 26, 2004 11:28 AM
To: Lucene Users List
Subject: Re: BooleanQuery - TooManyClauses
I think what Erik's asking is whether yo
Tuesday, October 26, 2004 11:43 AM
Subject: RE: BooleanQuery - TooManyClauses
>
>On Oct 25, 2004, at 6:35 PM, Angelov, Rossen wrote:
>> Why there is a limit on the number of clauses? and is there any harm in
>> setting MaxClauseCount to Integer.MAX_VALUE?
>
read on...
>
>> I'm using a Range Query on a field that represents dates and getting
>> BooleanQuery$TooManyClauses exception.
>> This is the query - +/article/createddateiso8601:[2003010100 TO
>> 2003123199]
>
>Do you really need to do ranges down to that t
on a field that represents dates and getting
BooleanQuery$TooManyClauses exception.
This is the query - +/article/createddateiso8601:[2003010100 TO
2003123199]
Do you really need to do ranges down to that time level? Or are you
really just concerned with date? If you indexed using YYY
Hi,
Why there is a limit on the number of clauses? and is there any harm in
setting MaxClauseCount to Integer.MAX_VALUE?
I'm using a Range Query on a field that represents dates and getting
BooleanQuery$TooManyClauses exception.
This is the query - +/article/createddateiso8601:[200301010
ailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 30. März 2004 09:25
An: Lucene Users List
Betreff: Re: BooleanQuery$TooManyClauses
hui wrote:
>Hi,
>I have a range query for the date like [20011201 To 20040201], it works
>fine for Lucene API 1.3 RC1. When I upgrade to 1.3 final, I got
&g
hui wrote:
Hi,
I have a range query for the date like [20011201 To 20040201], it works fine
for Lucene API 1.3 RC1. When I upgrade to 1.3 final, I got
"BooleanQuery$TooManyClauses" exception sometimes no matter the index is
created by 1.3RC1 or 1.3 final. Check on the email archive
Hi,
I have a range query for the date like [20011201 To 20040201], it works fine
for Lucene API 1.3 RC1. When I upgrade to 1.3 final, I got
"BooleanQuery$TooManyClauses" exception sometimes no matter the index is
created by 1.3RC1 or 1.3 final. Check on the email archive, it seems re
Correct.
As for side-effect, well, things will be slower, obviously :)
Increase the limit, perform a search, and see if it's still
sufficiently fast...that's what I would do. :)
Otis
--- Dror Matalon <[EMAIL PROTECTED]> wrote:
>
> This was raised in
>
>
http://www.mail-archive.com/[EMAIL PROTE
This was raised in
http://www.mail-archive.com/[EMAIL PROTECTED]/msg04696.html
and not really answered.
If I do
+(contents:luc* description:luc*)
Things work fine. However if I do
+(contents:car* description:car*)
I get the following exception
org.apache.lucene.search.BooleanQuery$TooM
17 matches
Mail list logo
