Re: toomanyclauses exception

2006-12-27 Thread Paul Elschot
On Wednesday 27 December 2006 16:53, Erick Erickson wrote: ... > 3> Look over the SrndQuery classes. I don't fully understand these, but they > certainly behave much differently in this area. Note that SrndQuery limits > wildcards to having at least three non-wildcard characters. In Lucene, the li

Re: toomanyclauses exception

2006-12-27 Thread Erick Erickson
Also, see the thread on this list titled "I just don't get wildcards at all" to see an extensive discussion of this issue, as well as wildcards in general. You might also search the archive for wildcards. The short form is that any wildcard (including prefix queries) expands under the covers to cr

Re: toomanyclauses exception

2006-12-27 Thread Paul Elschot
Chris, On Wednesday 27 December 2006 15:42, Chris Salem wrote: > Hi All, > > I'm getting a 'TooManyClauses' Exception and I'm not sure how to fix this. Here's a sample query that I'm using: > > +(+freeform_text:exhibit* +(+freeform_text:dispaly +freeform_text:event*) +(+freeform_text:sale* +f

Re: TooManyClauses exception in Lucene (1.4)

2006-03-17 Thread Erik Hatcher
On Mar 17, 2006, at 6:15 AM, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> wrote: Thanks to everyone for the explanation. Given that RangeQuery is clearly unsuitable for out requirements, ConstantScoreRangeQuery looks ideal. However, we're building our queries (at the moment) using QueryParser. I

RE: TooManyClauses exception in Lucene (1.4)

2006-03-17 Thread Tim.Wright
ad of a RangeQuery? Cheers, Tim. -Original Message- From: Yonik Seeley [mailto:[EMAIL PROTECTED] Sent: 16 March 2006 18:04 To: java-user@lucene.apache.org Subject: Re: TooManyClauses exception in Lucene (1.4) On 3/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I ha

Re: TooManyClauses exception in Lucene (1.4)

2006-03-16 Thread Erick Erickson
Thanks very much for your reply, I appreciate you taking the time. Erick

RE: TooManyClauses exception in Lucene (1.4)

2006-03-16 Thread Pasha Bizhan
Hi, > From: Doug Cutting [mailto:[EMAIL PROTECTED] > > The primary advantage of a RangeQuery is that the ranking > incorporates the degree of match of each term in the range, > which may be useful for wildcard-like searches but is useless > for date-like searches. Also, RangeQuery allows to

Re: TooManyClauses exception in Lucene (1.4)

2006-03-16 Thread Doug Cutting
Erick Erickson wrote: Could you point me to any explanation of *why* range queries expand this way? It's just what they do. They were contributed a long time ago, before things like RangeFilter or ConstantScoreRangeQuery were written. The latter are relatively recent additions to Lucene and

Re: TooManyClauses exception in Lucene (1.4)

2006-03-16 Thread Erick Erickson
When I read LIA, I was struck by this issue, and it seemed...er...like an easy mistake to make. Given that my impression of Lucene is that it's extraordinarily well designed, I assume that there must be a good reason for expanding range queries this way. Could you point me to any explanation of *w

Re: TooManyClauses exception in Lucene (1.4)

2006-03-16 Thread Yonik Seeley
On 3/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I had no idea that rangequery worked by enumerating every > possible value, that's terrifying. You could use either a RangeFilter or a ConstantScoreRangeQuery -Yonik http://incubator.apache.org/solr Solr, The Open Source Lucene Search Ser

RE: TooManyClauses exception in Lucene (1.4)

2006-03-16 Thread Tim.Wright
ery for "2005-01-" to catch an entire month in one query, etc? Cheers, Tim. -Original Message- From: Otis Gospodnetic [mailto:[EMAIL PROTECTED] Sent: 16 March 2006 17:26 To: java-user@lucene.apache.org Subject: Re: TooManyClauses exception in Lucene (1.4) Tim, This is possi

Re: TooManyClauses exception in Lucene (1.4)

2006-03-16 Thread Otis Gospodnetic
Tim, This is possible a lot of days: date:[2005-03-16 TO 2006-03-16] And if your 'date' field is more granular than 'a day', then this is a lot more hours/minutes/seconds/milliseconds. Your range query is expanded to all unique values in the range. This is probably in the FAQ, but if not, lo