NO_NORM and TOKENIZED

2008-03-04 Thread Tobias Hill
Hi, I am quite new to the Lucene API. I find the Field-constructor unintuitive. Maybe I have misunderstood it. Let's find out... It can be used either as: new Field("field", "data", Store.NO, TOKENIZED) or: new Field("field", "data", Store.NO, NO_NORM) As I understand it NO_NORM and TOKENIZED

SV: OutOfMemory-problems with SortComparatorSource / ScoreDocComparator

2007-11-08 Thread Tobias Hill
Alex Från: Tobias Hill [EMAIL PROTECTED] Skickat: den 8 november 2007 18:34 Till: java-user@lucene.apache.org Ämne: OutOfMemory-problems with SortComparatorSource / ScoreDocComparator Hi, We have implemented a custom sort following the pattern in Lucene in Action. Unfortun

OutOfMemory-problems with SortComparatorSource / ScoreDocComparator

2007-11-08 Thread Tobias Hill
Hi, We have implemented a custom sort following the pattern in Lucene in Action. Unfortunately this has led to quite serious memory problems. When analyzing those (with a profiler) it seems that there are as many remaining instances of our SortComparatorSource as there have been queries against th

2/3 of terms matched + coverage filter

2007-10-31 Thread Tobias Hill
My documents all hava a field with variables number of terms (but rather few): Doc1.field = "foo bar gro" Doc2.field = "foo bar gro mot slu" Now I would like to search using the terms "foo bar gro" Problem 1: I like to express that at least any two of the three terms must match. Do I have to const