Re: substring indexing to avoid 'TooManyClauses' exception

2007-11-14 Thread Erick Erickson
Hardy: Since your use-case is so restricted, I'd recommend that you just construct a filter. I think you'll find it's much faster than you'd think at first glance. Of course, "Your mileage may vary" Is there any equivalent phrase like "Your kilometerage may vary" ? Most of the discussion in the a

Re: substring indexing to avoid 'TooManyClauses' exception

2007-11-14 Thread Hardy Ferentschik
On Tue, 13 Nov 2007 16:12:26 +0100, Erick Erickson <[EMAIL PROTECTED]> wrote: Thanks for your help. I'm certainly not an expert on ranking and scoring, but I've got to assume that this approach influences scoring. No doubt. The question is if it matters for this particular use case. For th

Re: substring indexing to avoid 'TooManyClauses' exception

2007-11-13 Thread Erick Erickson
Hardy: I'm certainly not an expert on ranking and scoring, but I've got to assume that this approach influences scoring. Another issue is how you indexed multiple values. If you took a hint from the SynonymAnalyzer example in Lucene In Action, and indexed all the substrings with an increment of 0

substring indexing to avoid 'TooManyClauses' exception

2007-11-12 Thread Hardy Ferentschik
Hi, I have a question regarding the way I got around the 'TooManyClauses' exception when using wild card queries (http://wiki.apache.org/lucene-java/LuceneFAQ#head-06fafb5d19e786a50fb3dfb8821a6af9f37aa831). I am using Lucene in conjunction with Hibernate Search (http://www.hibernate.org/